Papers › EpiCoder: Encompassing Diversity and Complexity in Code Generation

EpiCoder: Encompassing Diversity and Complexity in Code Generation

8 Jan 2025arXiv:2501.04694archive 2025-07-28

Yaoxiang Wang, Haoling Li, Xin Zhang, Jie Wu, Xiao Liu, Wenxiang Hu, Zhongxin Guo, Yangyu Huang, Ying Xin, Yujiu Yang, Jinsong Su, Qi Chen, Scarlett Li

Effective instruction tuning is indispensable for optimizing code LLMs, aligning model behavior with user expectations and enhancing model performance in real-world applications. However, most existing methods focus on code snippets, which are limited to specific functionalities and rigid structures, restricting the complexity and diversity of the synthesized data. To address these limitations, we introduce a novel feature tree-based synthesis framework inspired by Abstract Syntax Trees (AST). Unlike AST, which captures syntactic structure of code, our framework models semantic relationships between code elements, enabling the generation of more nuanced and diverse data. The feature tree is constructed from raw data and refined iteratively to increase the quantity and diversity of the extracted features. This process enables the identification of more complex patterns and relationships within the code. By sampling subtrees with controlled depth and breadth, our framework allows precise adjustments to the complexity of the generated code, supporting a wide range of tasks from simple function-level operations to intricate multi-file scenarios. We fine-tuned widely-used base models to create the EpiCoder series, achieving state-of-the-art performance at both the function and file levels across multiple benchmarks. Notably, empirical evidence indicates that our approach shows significant potential in synthesizing highly complex repository-level code data. Further analysis elucidates the merits of this approach by rigorously assessing data complexity and diversity through software engineering principles and LLM-as-a-judge method.

PaperPDFCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 15 code samples harvested from 2 repositories linked to this paper: 14 ran (of which 0 constructed an object rather than computing a result; 14 with no instrument failure: 0 honoured, 0 violated, 14 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: found in paper text by Syntology: 15 samples from 2 repositories, 14 ran (14 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-24 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

microsoft/EpiCoder found in paper text by SyntologyMITSyntology: 1 sample, 1 ran (0 instrument-failed) · 0 unverified report
DeepLearnXMU/EpiCoder found in paper text by SyntologyMITSyntology: 14 samples, 13 ran (0 instrument-failed) · 1 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

15 samples harvested: 14 ran (of which 0 constructed an object rather than computing a result; 14 with no instrument failure: 0 honoured, 0 violated, 14 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

14ran
1unverified

Licence: 14 of the 15 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

microsoft/EpiCoder found in paper text by Syntology 1 sample, 1 ran (0 instrument-failed) · 0 unverified
extract_content in 17 papers gen/gen_code.py ran fingerprinted MIT (permissive) · d0f9fa36c5d6a449 · report fixture: signature solution:str/0/str · returned tuple · level recorded 2026-09-24
DeepLearnXMU/EpiCoder found in paper text by Syntology 14 samples, 13 ran (0 instrument-failed) · 1 unverified
custom_compare extract/extract_frequency_count.py ran MIT recorded; this copy not marked cleared · pointer only · 874482fd57d4cebe · report fixture: signature item:tuple/1/str · returned tuple · level recorded 2026-09-24
extract_content in 17 papers debug/run_test_iter0.py ran fingerprinted MIT recorded; this copy not marked cleared · pointer only · e3c9ed0f508ba2ea · report fixture: signature solution:str/0/str · returned tuple · level recorded 2026-09-24
extract_fields_from_formatted_text gen/gen_question.py ran fingerprinted MIT recorded; this copy not marked cleared · pointer only · fd8dc3b17db50e82 · report fixture: signature text:str/0/str · returned dict · level recorded 2026-09-25
form_feature_explanation evol/feature_evol.py ran fingerprinted MIT recorded; this copy not marked cleared · pointer only · 7237fedbb391f513 · report fixture: signature feature_list:list/1/str · returned str · level recorded 2026-09-24
get_features in 57 papers extract/construct_tree.py ran MIT recorded; this copy not marked cleared · pointer only · e6d8c07fb59f049e · report fixture: signature feature_freq_file:str/0/str · returned list · level recorded 2026-09-24
get_full_content extract/extract_features.py ran MIT recorded; this copy not marked cleared · pointer only · f46485f691c95440 · report fixture: signature d:dict/0/? · returned str · level recorded 2026-09-24
get_large_files utils/clear_code_debug_files.py ran fingerprinted MIT recorded; this copy not marked cleared · pointer only · 6150c6d6a7ed7b25 · report fixture: signature root_dir:str/0/str, size_threshold_mb:int/0/int · returned list · level recorded 2026-09-24
get_question in 12 papers gen/gen_code.py ran MIT recorded; this copy not marked cleared · pointer only · 91751933774cda1d · report fixture: signature item:dict/0/? · returned str · level recorded 2026-09-25
get_text in 18 papers evol/feature_evol.py ran MIT recorded; this copy not marked cleared · pointer only · 6e1c2fcd1329e0bc · report fixture: signature file_path:str/0/str · returned str · level recorded 2026-09-24
prune_to_top_n extract/extract_frequency_count.py ran MIT recorded; this copy not marked cleared · pointer only · 48e55621bbfcb75f · report fixture: signature freq_dict:dict/0/?, n:int/0/int, dict_min_size:int/0/int · returned dict · level recorded 2026-09-24
remove_keys evol/feature_evol.py ran MIT recorded; this copy not marked cleared · pointer only · c1811a3b989ac815 · report fixture: signature d:dict/0/?, keys_to_remove:list/1/str · returned dict · level recorded 2026-09-24
shorten_repeated_substrings call_api_local/call_api.py ran fingerprinted MIT recorded; this copy not marked cleared · pointer only · 42f192ac4d7c7b09 · report fixture: signature s:str/0/str · returned str · level recorded 2026-09-25
sort_feature_frequency extract/extract_frequency_count.py ran MIT recorded; this copy not marked cleared · pointer only · 993fdd25aaa46031 · report fixture: signature freq_dict:dict/0/? · returned dict · level recorded 2026-09-25
get_data_from_file extract/extract_features.py unverified MIT recorded; this copy not marked cleared · pointer only · 3d9347bfa4f46252 · report

Tasks

Code GenerationDiversity

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

BASEFocus

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections