Cited by 13Software Engineering ResearchNatural Language Processing TechniquesTopic Modeling

RepoTransBench: A Real-World Multilingual Benchmark for Repository-Level Code Translation

Open access
Wang, Yanli, Wang, Yanlin, Wang, Suiquan, Guo, Daya, Chen, Jiachi, Grundy, John, Liu, Xilin, Ma, Yuchi +3 more·2026·IEEE Transactions on Software Engineering

Abstract

Repository-level code translation refers to translating an entire code repository from one programming language to another while preserving the functionality of the source repository. Many benchmarks have been proposed to evaluate the performance of such code translators. However, previous benchmarks mostly provide fine-grained samples, focusing at either code snippet, function, or file-level code translation. Such benchmarks do not accurately reflect real-world demands, where entire repositories often need to be translated, involving longer code length and more complex functionalities. To address this gap, we propose a new benchmark, named RepoTransBench, which is a real-world multilingual repository-level code translation benchmark featuring 1,897 real-world repository samples across 13 language pairs with automatically executable test suites. Besides, we introduce RepoTransAgent, a general agent framework to perform repository-level code translation. We evaluate both our benchmark’s challenges and agent’s effectiveness using several methods and backbone LLMs, revealing that repository-level translation remains challenging, where the best-performing method achieves only a 32.8% success rate. Furthermore, our analysis reveals that translation difficulty varies significantly by language pair direction, with dynamic-to-static language translation being much more challenging than the reverse direction (achieving below 10% vs. static-to-dynamic at 45-63%). Finally, we conduct a detailed error analysis and highlight current LLMs’ deficiencies in repository-level code translation, which could provide a reference for further improvements. We provide the code and data athttps://github.com/DeepSoftwareAnalytics/RepoTransBench.

AI snapshot

Written from the paper’s full text.

TL;DR

RepoTransBench is a real-world multilingual repository-level code translation benchmark with 1,897 samples across 13 language pairs and automatically executable test suites, paired with RepoTransAgent, a ReAct-based agent framework. The best-performing method reaches only 32.8% success rate, and translation difficulty is strongly asymmetric: static-to-dynamic translation is much easier than dynamic-to-static.

Key findings

  • RepoTransBench contains 1,897 repository samples across 13 translation pairs and 7 languages, drawn from 970 unique projects. Samples average 23,966 tokens, 2,394 lines of code, 177 functions, 35 classes, and 163 import statements, with 87.9 cross-file and 1,443.7 intra-file dependencies; test suites achieve 81.89% line coverage and 72.61% branch coverage.
  • Repository-level translation remains challenging: the best configuration, RepoTransAgent with Claude or GPT-4.1, achieves 32.8% success rate. TranslationOnly mostly achieves 0.0% success, while ErrorFeedback reaches 11.3% with Claude and 15.6% with GPT-4.1; RepoTransAgent improves over ErrorFeedback by up to 21.5%.
  • Translation difficulty varies sharply by direction. Static-to-dynamic translations reach 45–63% success in the paper’s summary, while dynamic-to-static translations are typically below 10%; for example, Claude achieves 61.5% for C→Python, 63.0% for C++→Python, and 45.9% for Java→Python, whereas Python→Java reaches only 0.0–7.0% and Python→C++ only 0.0–9.9%.
  • Error analysis identifies five categories: E1 configuration file issues, E2 limited understanding ability issues, E3 incomplete generation issues, E4 language feature issues, and E5 encoding issues.

Methods

  • Data collection began with a questionnaire of 21 professional developers yielding 86 translation-pair requests; the authors selected 13 pairs across 7 languages, ranked GitHub repositories by stars, and retained repositories with more than 50 stars. Rule-based filtering enforced language dominance, popularity threshold, and package exclusion.
  • Benchmark construction used a multi-agent framework with four agents: Test Case Generator, Test Case Runner, Coverage Analyst, and Test Case Translator. It produced execution-based test suites and validated source repositories in runnable environments.
  • Evaluation used 8 LLMs (Qwen3-235B-A22B, Qwen3-235B-A22B-think, DeepSeek-Chat, DeepSeek-Reasoner, Claude-Sonnet-4, Gemini-2.5-Flash-Lite, GPT-4.1, o3-mini) and three methods (TranslationOnly, ErrorFeedback, RepoTransAgent), with metrics SR, CR, APR, and AMPR; generated code was executed in a Docker sandbox.

Limitations

  • Paper-stated internal threats: evaluated LLMs may not represent newer models, no fine-tuning was applied for repository-level translation, and the 13 translation pairs across 7 languages may not generalize to less common or domain-specific languages.
  • Paper-stated external threats: LLM generation variability may affect reproducibility; execution-based metrics using existing test suites may not capture all edge cases or guarantee complete semantic equivalence; repository filtering may bias toward popular, well-maintained projects; and benchmark temporal validity may decay as languages and frameworks evolve.
  • Evident from the text: test coverage is below 100% (81.89% line, 72.61% branch overall), so untested behavior may escape evaluation; some source languages have relatively few samples (e.g., Matlab 64, C# 97), which may limit per-pair conclusions.

Model-written summary. Check it against the paper before relying on it.

Integrity signals

Registry

Crossref · 10.1109/tse.2025.3645056

Cites

82 of 82 references verified0 citation errors · 0 not checkable

Statistics

Nothing to recompute.

Claims the paper makes

19 of 32 cited sources checked · 9 supported · 0 flagged · accuracy not yet measured

  • Premisecitation
    § I. INTRODUCTION · p. 1

    Snippet-level benchmarks such as CoST and XLCost focus on evaluating translation of program segments between two consecutive code comments.

    “snippetlevel code translation benchmarks, such as CoST [32], XLCost [33], typically focus on evaluating the translation of program segments located between two consecutive code comments.”
    Quote in the paperNot a substantial claim2 of 2 sources checked
    • cites [32] Zhu, 2022, Multilingual code snippets training for program translation source

      The Introduction (p. 1) identifies CoST as a benchmark for snippet-level translation and says its snippets are aligned by matching code comments across languages. Data Collection and Processing (p. 3) likewise describes using comments and their corresponding code to align snippets. Neither passage specifies that the evaluated segments lie between two consecutive comments; the paper also evaluates program-level translation. XLCost has a separate citation in the citing sentence and is not judged here. (LLM, conf=0.82)

      Experimental — accuracy not yet measured
    • cites [33] Zhu, 2022, Xlcost: A benchmark dataset for cross-lingual code intelligence source
  • Premisecitation
    § I. INTRODUCTION · p. 1

    Function-level benchmarks such as TransCoder-test, CodeXGLUE, and HumanEvalX focus on evaluating translation of a function.

    “Function-level code translation benchmarks, such as TransCoder-test [34], CodeXGLUE [35] and HumanEvalX [36], focus on evaluating the translation of a function.”
    Quote in the paperSubstantial claim2 of 3 sources checked
    • cites [34] Lachaux, 2020, Unsupervised translation of programming languages source
    • cites [35] Lu, 2021, CodeXGLUE: A machine learning benchmark dataset for code understanding and generation source
    • cites [36] 2025, humaneval-x

      Couldn’t be matched to a paper in Crossref, so it can’t be checked.

  • Premisecitation
    § C. Evaluation Metrics · p. 9

    Similarity-based metrics ignore the syntactic correctness and functional correctness of translations.

    “However, similarity-based metrics ignore the syntactic correctness and functional correctness of translations [34].”
    Quote in the paperSubstantial claim1 of 1 sources checked
    • cites [34] Lachaux, 2020, Unsupervised translation of programming languages source
  • Premisecitation
    § II. BACKGROUND · p. 4

    Real repositories typically contain existing test suites that can serve as validation mechanisms.

    “Furthermore, unlike artificially crafted datasets used in fine-grained translation [37], [38], real repositories typically contain existing test suites that can serve as valuable validation mechanisms.”
    Quote in the paperSubstantial claim2 of 2 sources checked
    • cites [37] Puri, 2021, CodeNet: A large-scale AI for code dataset for learning a diversity of coding tasks source

      The indexed passages discuss CodeNet datasets and online-judge acceptance metadata (Sections 5.1 and 9, pp. 6 and 19), not test suites in real repositories. Searches for existing test suites, repository validation, and test cases as correctness oracles found no passage supporting the attributed claim. (LLM, conf=0.74)

      Experimental — accuracy not yet measured
    • cites [38] source

      The Data Statistics section (page unavailable) says AVATAR uses publicly available AtCoder test cases to evaluate translation accuracy, supporting the use of existing tests for validation. The Introduction and Related Works mention collecting solutions from GitHub repositories, but do not say that real repositories typically contain test suites or that repository test suites supplied AVATAR’s tests. (LLM, conf=0.78)

      Experimental — accuracy not yet measured
  • Premisereasoning
    § VIII. RELATED WORK · p. 14

    Pan et al. [1] do not provide a sufficient number of repositories and corresponding automatic test suites for evaluation.

    “However, they do not provide a sufficient number of repositories and corresponding automatic test suites for evaluation.”
    Quote in the paperSubstantial claim1 of 1 sources checked
    • cites [1] source

      The Dataset Collection and Pre-Processing section identifies only two real-world projects, Apache Commons CLI and Click, which supports the concern about the number of repositories. But it says the projects have unit tests and does not assess whether the number of repositories or corresponding test suites is sufficient for evaluation. It also notes that the translated projects never reached test execution because the code was syntactically incorrect. (LLM, conf=0.83)

      Experimental — accuracy not yet measured
  • Classified as probably not a substantial claim. 44
  • May combine two claims. 42
  • Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.

    Premisecitation
    § I. INTRODUCTION · p. 1

    Code translation facilitates refactoring outdated languages, transitions to faster languages, and supports programming language migration.

    “It facilitates the refactoring of code written in outdated languages [10], transitions from simpler but slower languages to more complex and faster ones [11], and supports programming language migration in software development [12]-[19].”
    Quote in the paperNot a substantial claim1 of 3 sources checked
    • cites [10] Aggarwal, 2015, Using machine translation for converting python 2 to python 3 code source
    • cites [11] Szafraniec, 2022, Code translation with compiler representations source
    • cites [12]-[19]

      Couldn’t be matched to a paper in Crossref, so it can’t be checked.

  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Premisecitation
    § I. INTRODUCTION · p. 1

    File-level benchmarks including CodeNet, Avatar, CodeScope, and CodeTransOcean evaluate translation of a complete program file.

    “File-level code translation benchmarks which include CodeNet [37], Avatar [38], CodeScope [39] and CodeTransOcean [40] refer to evaluating the translation of a complete program file.”
    Quote in the paperNot a substantial claim2 of 3 sources checked
    • cites [37] Puri, 2021, CodeNet: A large-scale AI for code dataset for learning a diversity of coding tasks source

      The ‘Further Uses of CodeNet’ section (p. 19) says CodeNet may be used for program translation, supporting its inclusion as a translation dataset. The passages do not establish that it evaluates translation of a complete program file, or describe Avatar, CodeScope, and CodeTransOcean as file-level benchmarks. (LLM, conf=0.78)

      Experimental — accuracy not yet measured
    • cites [38] source
    • cites [39], [40]

      Couldn’t be matched to a paper in Crossref, so it can’t be checked.

  • Classified as probably not a substantial claim. May combine two claims.

    Premisecitation
    § I. INTRODUCTION · p. 1

    Pan et al. manually studied two open-source repositories and found current LLMs struggle to perform code translation for entire repositories.

    “Recently, Pan et al. [1] manually study two opensource repositories (Apache Commons CLI [41] and Python Click [42]), and find that current LLMs struggle to perform code translation for entire repositories.”
    Quote in the paperSubstantial claim1 of 1 sources checked
  • Classified as probably not a substantial claim. May combine two claims.

    Premisecitation
    § II. BACKGROUND · p. 4

    Pan et al. found advanced LLMs are largely ineffective at repository-level translation, with success rates of 8.1% for GPT-4 and 0% for the rest of the models.

    “Pan et al. [1] attempt to perform mutual conversion between Python and Java projects [41], [42], but find that the advanced LLMs are largely ineffective, with success rates of 8.1% for GPT-4 and 0% for the rest of the models.”
    Quote in the paperSubstantial claim1 of 1 sources checked
  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Premisecitation
    § VIII. RELATED WORK · p. 14

    AlphaTrans [95] is a neuro-symbolic compositional technique that decomposes repositories into fragments and translates them in reverse call order with GraalVM-based validation.

    “AlphaTrans [95] is proposed as a neuro-symbolic compositional technique that decomposes repositories into fragments and translates them in reverse call order with GraalVM-based validation.”
    Quote in the paperNot a substantial claim1 of 1 sources checked
    • cites [95] Gong, 2025, Tracy: Benchmarking execution efficiency of LLM-based code translation source

      The References section identifies AlphaTrans as a neuro-symbolic compositional approach to repository-level code translation and validation. Our copy does not describe repository fragmentation, translation in reverse call order, or GraalVM-based validation; searches for those details found no supporting passage. (LLM, conf=0.85)

      Experimental — accuracy not yet measured
  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Premisecitation
    § VIII. RELATED WORK · p. 14

    Pan et al. [1] ignore resource and configuration files.

    “Besides, the resource and configuration files are ignored in this research.”
    Quote in the paperNot a substantial claim1 of 1 sources checked
    • cites [1] source

      Dataset Collection and Pre-Processing describes translating Java and Python code broken into classes and files, and says comments were removed. It does not say whether resource or configuration files were ignored. Searches for those files and for non-code-file exclusions found no passage that settles the claim. (LLM, conf=0.72)

      Experimental — accuracy not yet measured
  • Classified as probably not a substantial claim.

    Premisecitation
    § VIII. RELATED WORK · p. 14

    Pan et al. [1] manually studied two open-source repositories (Apache Commons CLI and Python Click) and found that current LLMs struggle to complete the translation tasks of entire repositories.

    “Recently, pan et al. [1] manually study two open-source repositories (Apache Commons CLI [41] and Python Click [42]) and find that current LLMs struggle to complete the translation tasks of entire repositories.”
    Quote in the paperSubstantial claim1 of 3 sources checked
    • cites [1] source
    • cites [41] 2025, Apache commons cli

      Couldn’t be matched to a paper in Crossref, so it can’t be checked.

    • cites [42] 2025, Click

      Couldn’t be matched to a paper in Crossref, so it can’t be checked.

  • May combine two claims.

    Findingown data
    § RepoTransBench: A Real-World Multilingual Benchmark for Repository-Level Code Translation · p. 1

    Repository-level translation remains challenging; the best-performing method achieves only a 32.8% success rate.

    “revealing that repositorylevel translation remains challenging, where the best-performing method achieves only a 32.8% success rate.”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Findingown data
    § RepoTransBench: A Real-World Multilingual Benchmark for Repository-Level Code Translation · p. 1

    RepoTransBench is a real-world multilingual repository-level code translation benchmark with 1,897 repository samples across 13 translation pairs covering 7 programming languages and automatic execution-based test suites for compilability and functional correctness.

    “we propose a new benchmark, named RepoTransBench, which is a real-world multilingual repository-level code translation benchmark featuring 1,897 real-world repository samples across 13 language pairs with automatically executable test suites.”
    • Also stated in: § I. INTRODUCTION · p. 2 · plain
      “RepoTransBench encompasses 1,897 repository samples across 13 translation pairs covering 7 programming languages, providing automatic execution-based test suites to evaluate both compilability and functional correctness of translated repositories.”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Findingown data
    § RepoTransBench: A Real-World Multilingual Benchmark for Repository-Level Code Translation · p. 1

    Translation difficulty varies significantly by language pair direction; dynamic-to-static translation is much more challenging than the reverse direction, achieving below 10% versus static-to-dynamic at 45-63%.

    “translation difficulty varies significantly by language pair direction, with dynamic-to-static language translation being much more challenging than the reverse direction (achieving below 10% vs. static-to-dynamic at 45-63%).”
    Quote in the paperSubstantial claim
  • Classified as probably not a substantial claim.

    Findingnone given
    § RepoTransBench: A Real-World Multilingual Benchmark for Repository-Level Code Translation · p. 1

    RepoTransAgent is a general agent framework to perform repository-level code translation.

    “Besides, we introduce RepoTransAgent, a general agent framework to perform repository-level code translation.”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Findingown data
    § D. Statistics of RepoTransBench · p. 7

    JavaScript has the highest coverage (93.56% line, 88.12% branch) and Matlab the lowest (61.33% line, 55.99% branch).

    “with JavaScript achieving the highest coverage (93.56% line coverage, 88.12% branch coverage) and Matlab showing the most room for improvement (61.33% line coverage, 55.99% branch coverage).”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingown data
    § A. RQ1: Performance of LLM-based Translation Methods · p. 10

    TranslationOnly approaches achieve partial success, with compilation rates ranging from 10.9% to 33.3% and nonzero average pass rates.

    “However, these approaches can still achieve partial success, with compilation rates ranging from 10.9% (DeepSeek-Reasoner) to 33.3% (o3mini), and some test cases passing as evidenced by nonzero APR values.”
    • Also stated in: § A. RQ1: Performance of LLM-based Translation Methods · p. 10 · plain
      “However, it can still achieve partial success with some repositories being compilable and passing individual test cases”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Findingown data
    § B. RQ2: Performance Differences Across translation pairs · p. 11

    o3-mini demonstrates exceptional performance on C→Rust translation with 67.2% success rate, outperforming Claude (47.5%) and GPT-4.1 (47.5%).

    “Most notably, o3-mini demonstrates exceptional performance on C → Rust translation with 67.2% success rate, significantly outperforming leading models like Claude (47.5%) and GPT-4.1 (47.5%) on the same pair.”
    Quote in the paperSubstantial claim
  • Probably not a substantial claim: may not pass S4 (based).

    Findingnone given
    § I. INTRODUCTION · p. 2

    RepoTransBench demonstrates substantially higher context and dependency complexity than previous benchmarks.

    “RepoTransBench demonstrates substantially higher context and dependency complexity than previous benchmarks.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingown data
    § D. Statistics of RepoTransBench · p. 7

    The dataset encompasses 970 unique projects, with Python most represented (684 samples from 171 projects) followed by Java (438 samples from 146 projects).

    “Our dataset encompasses 970 unique projects, with Python being the most represented source language (684 samples from 171 projects) followed by Java (438 samples from 146 projects).”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingown data
    § D. Statistics of RepoTransBench · p. 6

    RepoTransBench has an average of 87.9 cross-file dependencies and 1,443.7 intra-file dependencies.

    “RepoTransBench has an average of 87.9 cross-file dependencies and 1,443.7 intra-file dependencies.”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Findingown data
    § I. INTRODUCTION · p. 2

    RepoTransBench repositories contain an average of 23,966 tokens, 2,394 lines of code, 177 functions, 35 classes, and 163 import statements.

    “Our benchmark demonstrates higher complexity than previous work, with repositories containing an average of 23,966 tokens, 2,394 lines of code, 177 functions, 35 classes, and 163 import statements.”
    • Also stated in: § D. Statistics of RepoTransBench · p. 6 · boosted
      “Each sample contains an average of 177 functions, 35 classes, and 163 import statements, demonstrating the complex interdependencies and architectural patterns inherent in real-world software projects.”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Findingown data
    § B. RQ2: Performance Differences Across translation pairs · p. 11

    Claude particularly excels at translating to Python, achieving the highest success rates for C → Python, C++ → Python, and Matlab → Python.

    “Claude shows strong performance across most translation pairs but particularly excels at translating to Python (achieving the highest success rates for C → Python, C++ → Python, and Matlab → Python)”
    Quote in the paperNot a substantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing), S4 (based).

    Findingnone given
    § A. Data Collection · p. 4

    Interest in Python → Go translation reflects organizational shifts toward Go's concurrency model and deployment simplicity for backend services.

    “The interest in Python → Go translation similarly reflects organizational shifts toward Go's concurrency model and deployment simplicity for backend services.”
    Quote in the paperNot a substantial claim
  • Probably not a substantial claim: may not pass S4 (based). May combine two claims.

    Findingnone given
    § IV. REPOTRANSAGENT · p. 7

    RepoTransAgent adopts a holistic understanding of entire software repositories, enabling it to handle complex interdependencies, maintain project structure, and ensure functional correctness during translation.

    “RepoTransAgent adopts a holistic understanding of entire software repositories, enabling it to handle complex interdependencies, maintain project structure, and ensure functional correctness during translation.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingown data
    § B. RQ2: Performance Differences Across translation pairs · p. 11

    Gemini demonstrates highly inconsistent performance, achieving strong compilation rates for some pairs (95.8% for JavaScript → Python compilation) but near-zero functional success rates.

    “In contrast, Gemini demonstrates highly inconsistent performance, achieving strong compilation rates for some pairs (95.8% for JavaScript → Python compilation) but nearzero functional success rates, indicating potential gaps in understanding semantic equivalence across languages.”
    Quote in the paperSubstantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Findingnone given
    § C. Multi-Agent-Based Test Suite Construction · p. 5

    The multi-agent framework comprises four specialized agents: Test Case Generator, Test Case Runner, Coverage Analyst, and Test Case Translator.

    “The framework comprises four specialized agents that work collaboratively to ensure high-quality benchmark construction: Test Case Generator, Test Case Runner, Coverage Analyst, and Test Case Translator.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingown data
    § B. RQ2: Performance Differences Across translation pairs · p. 10

    Python-to-static-language translations face severe challenges, with Python→Java achieving 0.0-7.0% success rates, Python→C++ 0.0-9.9%, and Python→Rust 1.2-26.3%.

    “Conversely, Python-to-static-language translations face severe challenges across all evaluated models. Python → Java achieves only 0.0-7.0% success rates, Python → C++ reaches merely 0.0-9.9%, and Python → Rust performs between 1.226.3%.”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Findingnone given
    § I. INTRODUCTION · p. 2

    RepoTransAgent can analyze repository structures, understand cross-file dependencies, manage configuration files, and iteratively refine translations based on execution feedback.

    “RepoTransAgent can analyze repository structures, understand cross-file dependencies, manage configuration files, and iteratively refine translations based on execution feedback.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingown data
    § D. Statistics of RepoTransBench · p. 6

    RepoTransBench contains 1,897 translation samples across 13 translation pairs, significantly surpassing the scale of previous work.

    “Our benchmark contains 1,897 translation samples across 13 translation pairs, significantly surpassing the scale of previous work.”
    Quote in the paperSubstantial claim
  • Classified as probably not a substantial claim.

    Findingnone given
    § I. INTRODUCTION · p. 2

    RepoTransAgent operates through five core capabilities: reading files, creating files, executing commands, searching content, and marking completion.

    “The agent operates through five core capabilities: reading files, creating files, executing commands, searching content, and marking completion, enabling repository-level translation through a reasoning-action loop that adapts to diverse programming language ecosystems.”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Findingown data
    § A. RQ1: Performance of LLM-based Translation Methods · p. 9

    With Claude, RepoTransAgent achieves 32.8% SR compared to 0.0% for TranslationOnly and 11.3% for ErrorFeedback; with GPT-4.1, it achieves 32.8% SR versus 0.0% and 15.6% respectively.

    “For instance, with Claude, RepoTransAgent achieves 32.8% SR compared to 0.0% for TranslationOnly and 11.3% for ErrorFeedback, while with GPT-4.1, it achieves 32.8% SR versus 0.0% and 15.6% respectively.”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Findingreasoning
    § B. RQ2: Performance Differences Across translation pairs · p. 10

    Translations from static languages (C, C++, Java) to Python consistently achieve high success rates across most models (e.g., Claude 61.5% for C→Python, 63.0% for C++→Python, 45.9% for Java→Python; GPT-4.1 54.9%, 55.2%, 58.2% respectively).

    “Translations from static languages (C, C++, Java) to Python consistently achieve high success rates across most models: Claude achieves 61.5% for C → Python, 63.0% for C++ → Python, and 45.9% for Java → Python, while GPT-4.1 reaches 54.9%, 55.2%, and 58.2% respectively.”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Findingown data
    § D. Statistics of RepoTransBench · p. 6

    Cross-file dependencies range from 2.1 in Matlab to 156.9 in Java, while intra-file dependencies range from 600.9 in C# to 2,494.4 in C.

    “cross-file dependencies range from 2.1 in Matlab to 156.9 in Java, while intra-file dependencies range from 600.9 in C# to 2,494.4 in C.”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Findingown data
    § D. Statistics of RepoTransBench · p. 6

    The average sample in RepoTransBench contains 23,966 tokens and 2,394 lines of code, representing an increase of over 95× in tokens and 108× in lines compared to xCodeEval (209 tokens and 22 lines per sample).

    “The average sample in our benchmark contains 23,966 tokens and 2,394 lines of code, representing a dramatic increase of over 95× in tokens and 108× in lines compared to the largest previous benchmark (xCodeEval with 209 tokens and 22 lines per sample).”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Findingown data
    § A. RQ1: Performance of LLM-based Translation Methods · p. 9

    Repository-level code translation remains a challenging task for current LLMs, with the best-performing configuration (RepoTransAgent with Claude and GPT-4.1) achieving only 32.8% success rate.

    “The results demonstrate that repository-level code translation remains a challenging task for current LLMs. Even the best-performing configuration (RepoTransAgent with Claude and GPT-4.1) achieves only 32.8% success rate”
    • Also stated in: § A. RQ1: Performance of LLM-based Translation Methods · p. 10 · plain
      “However, repository-level code translation remains highly challenging for current LLM-based methods, with the best-performing method achieving only a 32.8% success rate.”
    Quote in the paperSubstantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing), S4 (based).

    Findingnone given
    § A. Data Collection · p. 4

    C → Rust translation demand indicates growing adoption of Rust for systems programming.

    “Meanwhile, C → Rust translation demand indicates the growing adoption of Rust for systems programming, where developers aim to modernize legacy C codebases while gaining memory safety guarantees.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingown data
    § A. Data Collection · p. 4

    The survey received responses from 21 professional developers, comprising 86 requests for specific translation pairs.

    “We receive responses from 21 professional developers, comprising 86 requests for specific translation pairs.”
    Quote in the paperSubstantial claim
    • Rests on an assumption: The 21 surveyed professional developers' translation-pair requests represent real-world developer needs.
  • May combine two claims.

    Findingown data
    § I. INTRODUCTION · p. 2

    RepoTransAgent consistently outperforms baseline approaches, demonstrating improvements of up to 21.5% over the error feedback method.

    “However, our RepoTransAgent framework consistently outperforms baseline approaches, demonstrating improvements of up to 21.5% over the error feedback method.”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Findingnone given
    § I. INTRODUCTION · p. 2

    RepoTransAgent is based on the ReAct (Reasoning + Acting) paradigm and is specifically designed to solve repository-level code translation problems.

    “RepoTransAgent addresses general translation challenges through an intelligent agent framework based on the ReAct (Reasoning + Acting) paradigm, specifically designed to solve repository-level code translation problems.”
    Quote in the paperSubstantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Findingreasoning
    § A. Data Collection · p. 4

    There is sustained interest in Python → Java translation.

    “The sustained interest in Python → Java translation reflects the common enterprise pattern where Python prototypes must be productionized in Java environments for scalability and integration with existing enterprise systems.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingown data
    § C. RQ3: Impact of Dependency Complexity · p. 12

    Successful translations typically involve repositories with fewer lines of code, fewer functions, and fewer classes.

    “The pattern extends to basic size metrics, where successful translations typically involve repositories with fewer lines of code, fewer functions, and fewer classes.”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Findingown data
    § IX. CONCLUSION · p. 14

    There is strong directional asymmetry in translation difficulty, with static-to-dynamic translation achieving 45-63% success and the reverse direction below 10%.

    “We also observe strong directional asymmetry in translation difficulty (static-todynamic achieving 45-63% vs. reverse direction below 10%)”
    Quote in the paperSubstantial claim
  • Probably not a substantial claim: may not pass S2 (checkable), S3 (load-bearing).

    Premisecitation
    § I. INTRODUCTION · p. 1

    High-quality synthetic data has become essential for further improving LLMs' performance.

    “High-quality synthetic data has become essential for further improving LLMs' performance [5], [6].”
    Quote in the paperNot a substantial claim0 of 1 sources checked
    • cites [5], [6]

      Couldn’t be matched to a paper in Crossref, so it can’t be checked.

  • Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.

    Premisecitation
    § I. INTRODUCTION · p. 1

    By leveraging code translation, vast amounts of code in various programming languages can be transformed into high-quality training data, offering a viable solution to data scarcity.

    “By leveraging code translation, vast amounts of code written in various programming languages can be transformed into high-quality training data, offering a viable solution to this scarcity [7]-[9].”
    Quote in the paperNot a substantial claim0 of 1 sources checked
    • cites [7]-[9]

      Couldn’t be matched to a paper in Crossref, so it can’t be checked.

  • Probably not a substantial claim: may not pass S4 (based).

    Premisenone given
    § I. INTRODUCTION · p. 1

    Existing repository-level translation studies are severely limited in scope, with most work examining only one or two translation pairs and a handful of repositories.

    “Existing repository-level translation studies are severely limited in scope, with most work examining only one or two translation pairs and a handful of repositories.”
    Quote in the paperNot a substantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.

    Premisecitation
    § I. INTRODUCTION · p. 1

    With the popularity of LLMs, researchers are trying to translate code with LLMs, yielding promising results.

    “With the popularity of large language models (LLMs), researchers are trying to translate code with LLMs, yielding promising results [29]-[31].”
    Quote in the paperNot a substantial claim0 of 1 sources checked
    • cites [29]-[31]

      Couldn’t be matched to a paper in Crossref, so it can’t be checked.

  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Premisecitation
    § I. INTRODUCTION · p. 1

    Automatic code translation can significantly reduce manual effort.

    “Automatic code translation can significantly reduce manual effort and has thus garnered widespread attention in recent years [20][28].”
    Quote in the paperNot a substantial claim0 of 1 sources checked
    • cites [20][28]

      Couldn’t be matched to a paper in Crossref, so it can’t be checked.

  • Probably not a substantial claim: may not pass S4 (based). May combine two claims.

    Interpretationreasoning
    § II. BACKGROUND · p. 4

    Successful repository translation necessitates appropriate configuration of ecosystem-specific files and comprehensive resource migration beyond source code.

    “Additionally, successful repository translation necessitates appropriate configuration of ecosystem-specific files and comprehensive resource migration beyond source code, where resource files that perform I/O operations with code components must be carefully handled and potentially transformed to maintain functional equivalence.”
    Quote in the paperNot a substantial claim
  • Probably not a substantial claim: may not pass S2 (checkable), S3 (load-bearing).

    Interpretationreasoning
    § B. RQ2: Performance Differences Across translation pairs · p. 11

    The specialization patterns likely reflect the LLMs' training data composition and architectural biases.

    “likely reflecting their training data composition and architectural biases.”
    Quote in the paperNot a substantial claim
  • Probably not a substantial claim: may not pass S4 (based).

    Premisenone given
    § I. INTRODUCTION · p. 2

    Current translation methods often rely on language-specific heuristics tailored to particular translation pairs, making them difficult to generalize across diverse language combinations.

    “Current translation methods often rely on language-specific heuristics tailored to particular translation pairs, making them difficult to generalize across diverse programming language combinations.”
    Quote in the paperNot a substantial claim
    • Rests on an assumption: Current translation methods often rely on language-specific heuristics tailored to particular translation pairs.
  • Classified as probably not a substantial claim. May combine two claims.

    Study design and conductnone given
    § A. Data Collection · p. 4

    To ensure repository quality, repositories were ranked by star count and only those with more than 50 stars were retained.

    “To ensure repository quality, we rank repositories by star count and retain only those with more than 50 stars.”
    Quote in the paperSubstantial claim
    • Rests on an assumption: A repository's star count above 50 indicates sufficient code quality and practical relevance.
  • Classified as probably not a substantial claim. May combine two claims.

    Study design and conductreasoning
    § B. Rule-Based Filtering · p. 5

    For Python repositories, they required Python code comprises the largest share, the repository exceeds the popularity threshold, and it does not have substantial dependencies on excluded packages such as PyTorch, TensorFlow, and NLTK.

    “To illustrate, for Python repositories, we require that (1) Python code comprises the largest share of the codebase, (2) the repository exceeds the popularity threshold, and (3) it does not have substantial dependencies on excluded packages (e.g., PyTorch, TensorFlow, NLTK).”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Interpretationreasoning
    § B. RQ2: Performance Differences Across translation pairs · p. 11

    Training data distribution and architectural choices significantly influence model performance on specific language combinations.

    “These patterns suggest that training data distribution and architectural choices significantly influence model performance on specific language combinations.”
    Quote in the paperSubstantial claim
  • Probably not a substantial claim: may not pass S4 (based).

    Premisenone given
    § I. INTRODUCTION · p. 2

    Repository-level code translation benchmark construction is labor-intensive, requiring extensive manual effort to ensure executability, generate test suites, validate correctness, and manage dependencies.

    “Repository-level code translation benchmark construction is labor-intensive, requiring extensive manual effort to ensure repository executability, generate comprehensive test suites, validate functional correctness, and manage complex dependencies.”
    Quote in the paperNot a substantial claim
    • Rests on an assumption: Repository-level code translation benchmark construction is labor-intensive.
  • Probably not a substantial claim: may not pass S4 (based).

    Premisenone given
    § II. BACKGROUND · p. 4

    Real-world code repositories typically include numerous functions, classes, and import statements, requiring translators to understand entire repository context and intricate interdependencies across files and modules.

    “Real-world code repositories typically include numerous functions, classes, and import statements to realize complex functionalities, requiring translators to understand the entire repository context rather than isolated code fragments with intricate interdependencies between components across multiple files and modules.”
    Quote in the paperNot a substantial claim
  • Classified as probably not a substantial claim. May combine two claims.

    Interpretationreasoning
    § II. BACKGROUND · p. 4

    Repository-level code translation presents three fundamentally different challenges: challenging context management, complex dependency analysis, and difficult environment setup.

    “Compared with previous fine-grained code translation granularity, repository-level code translation presents three fundamentally different challenges: challenging context management, complex dependency analysis, and difficult environment setup.”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Interpretationcitation
    § II. BACKGROUND · p. 4

    Repository-level translation requires fundamentally different approaches from fine-grained translation because current LLM-based methods struggle with large-scale context management, complex dependency analysis, and comprehensive environment configuration.

    “This stark performance gap reveals that repository-level translation requires fundamentally different approaches from fine-grained translation, as current LLM-based methods struggle with the challenges of large-scale context management, complex dependency analysis, and comprehensive environment configuration that are inherent to repository-level code translation.”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Premisenone given
    § D. Statistics of RepoTransBench · p. 6

    Previous benchmarks typically contain at most 2 functions per sample and rarely include classes or substantial import dependencies.

    “In contrast, previous benchmarks typically contain at most 2 functions per sample and rarely include classes or substantial import dependencies.”
    Quote in the paperNot a substantial claim
  • Classified as probably not a substantial claim.

    Study design and conductreasoning
    § B. Rule-Based Filtering · p. 5

    Rule-based filtering retained only repositories where the target language constitutes the largest proportion of the codebase.

    “Rule 1: Language Dominance. We retain only repositories where the target language constitutes the largest proportion of the codebase.”
    Quote in the paperSubstantial claim
  • Probably not a substantial claim: may not pass S2 (checkable), S4 (based). May combine two claims.

    Premisereasoning
    § I. INTRODUCTION · p. 2

    Real-world code repository migration often requires proper handling of resources and correct configuration management.

    “A real-world code repository migration often requires proper handling of resources and correct configuration management.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Premisenone given
    § II. BACKGROUND · p. 3

    Neural network-based approaches still struggle with cross-file dependencies and large-scale context management, limiting their effectiveness beyond file-level translation.

    “However, neural network-based approaches still struggle with cross-file dependencies and large-scale context management, limiting their effectiveness beyond file-level translation.”
    Quote in the paperNot a substantial claim
  • Probably not a substantial claim: may not pass S4 (based).

    Premisenone given
    § I. INTRODUCTION · p. 2

    Many programming language repositories contain configuration files and resource files, such as CMakeLists.txt for C++ and pom.xml for Java.

    “Many programming language repositories contain configuration files and resource files, such as CMakeLists.txt for C++ and pom.xml for Java.”
    Quote in the paperNot a substantial claim
    • Rests on an assumption: Many programming language repositories contain configuration files and resource files.
  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Study design and conductreasoning
    § B. Rule-Based Filtering · p. 5

    Rule-based filtering excluded repositories that depend on packages difficult to translate into target languages.

    “Rule 3: Package Exclusion. We exclude repositories that depend on packages difficult to translate into target languages.”
    Quote in the paperNot a substantial claim
  • Classified as probably not a substantial claim.

    Study design and conductreasoning
    § B. Rule-Based Filtering · p. 5

    Rule-based filtering filtered repositories based on a minimum star threshold θ_star.

    “Rule 2: Popularity Threshold. We filter repositories based on a minimum star threshold θ star to ensure code quality and practical relevance.”
    Quote in the paperSubstantial claim
  • Probably not a substantial claim: may not pass S2 (checkable), S4 (based).

    Study design and conductreasoning
    § VII. THREATS TO VALIDITY · p. 14

    The focus on fundamental language features and well-established frameworks ensures that the findings remain relevant across reasonable time horizons.

    “However, our focus on fundamental language features and well-established frameworks ensures that our findings remain relevant across reasonable time horizons.”
    Quote in the paperNot a substantial claim
    • Rests on an assumption: Programming languages, frameworks, and development practices evolve continuously.
  • Probably not a substantial claim: may not pass S3 (load-bearing), S4 (based).

    Interpretationnone given
    § VII. THREATS TO VALIDITY · p. 14

    The automated benchmark construction framework can facilitate future updates and extensions to maintain benchmark currency.

    “The automated benchmark construction framework we develop can facilitate future updates and extensions to maintain benchmark currency.”
    Quote in the paperNot a substantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Interpretationreasoning
    § D. RQ4: Error Analysis · p. 13

    Incomplete generation issues can be fixed by regenerating or replacing them with stronger LLMs.

    “Then we can fix these issues by regenerating or replacing them with stronger LLMs.”
    Quote in the paperNot a substantial claim
  • Classified as probably not a substantial claim. May combine two claims.

    Study design and conductreasoning
    § VII. THREATS TO VALIDITY · p. 14

    The study employs consistent experimental settings and analyzes performance patterns across multiple samples rather than isolated instances to mitigate generation variability.

    “To mitigate this threat, we employ consistent experimental settings and analyze performance patterns across multiple samples rather than isolated instances.”
    Quote in the paperSubstantial claim
    • Rests on an assumption: Large language models exhibit inherent randomness in their outputs.
  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Study design and conductnone given
    § VII. THREATS TO VALIDITY · p. 13

    No fine-tuning methods were applied to the LLMs specifically for repository-level translation.

    “Additionally, we do not apply fine-tuning methods to these LLMs specifically for repository-level translation, which may impact their performance.”
    Quote in the paperNot a substantial claim
  • Classified as probably not a substantial claim. May combine two claims.

    Study design and conductnone given
    § VII. THREATS TO VALIDITY · p. 14

    Passing all test cases provides strong evidence of functional correctness but may not capture all edge cases or guarantee complete semantic equivalence.

    “While passing all test cases provides strong evidence of functional correctness, it may not capture all edge cases or guarantee complete semantic equivalence.”
    Quote in the paperSubstantial claim
    • Rests on an assumption: Real-world test suites from production repositories provide more realistic evaluation scenarios compared to artificially constructed benchmarks.
  • Classified as probably not a substantial claim.

    Study design and conductnone given
    § VII. THREATS TO VALIDITY · p. 14

    The evaluation focuses on objective metrics (compilation success, test passage) that are less susceptible to generation variance compared to subjective quality assessments.

    “Additionally, our evaluation focuses on objective metrics (compilation success, test passage) that are less susceptible to generation variance compared to subjective quality assessments.”
    Quote in the paperSubstantial claim
    • Rests on an assumption: Large language models exhibit inherent randomness in their outputs.
  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Premisecitation
    § VIII. RELATED WORK · p. 14

    TRACY [96] is a benchmark proposed to evaluate the execution efficiency of function-level code translation.

    “TRACY [96] is a benchmark proposed to evaluate the execution efficiency of function-level code translation.”
    Quote in the paperNot a substantial claim0 of 1 sources checked
    • cites [96]

      Couldn’t be matched to a paper in Crossref, so it can’t be checked.

  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Interpretationreasoning
    § D. RQ4: Error Analysis · p. 13

    Providing LLMs with more information about language features in the prompt may help improve translation performance.

    “Providing LLMs with more information about the language features in the prompt may help improve the translation performance.”
    Quote in the paperNot a substantial claim
  • Probably not a substantial claim: may not pass S4 (based). May combine two claims.

    Study design and conductnone given
    § VII. THREATS TO VALIDITY · p. 13

    The language selection is based on TIOBE rankings and developer survey data, ensuring relevance to real-world translation needs.

    “However, our language selection is based on TIOBE rankings and developer survey data, ensuring relevance to real-world translation needs.”
    Quote in the paperNot a substantial claim
  • Classified as probably not a substantial claim.

    Study design and conductreasoning
    § VII. THREATS TO VALIDITY · p. 14

    The bias toward well-maintained, popular repositories is intentional to ensure benchmark quality and practical relevance.

    “This bias is intentional to ensure benchmark quality and practical relevance, as successful repository-level translation tools should prioritize handling well-structured, maintainable codebases that represent common development scenarios.”
    Quote in the paperSubstantial claim
    • Rests on an assumption: Successful repository-level translation tools should prioritize handling well-structured, maintainable codebases that represent common development scenarios.
72 of 72
  • The paper relies on this without support.

    Repository-level code translation benchmark construction is labor-intensive.

    “Repository-level code translation benchmark construction is labor-intensive, requiring extensive manual effort to ensure repository executability, generate comprehensive test suites, validate functional correctness, and manage complex dependencies.”
  • The paper relies on this without support.

    Current translation methods often rely on language-specific heuristics tailored to particular translation pairs.

    “Current translation methods often rely on language-specific heuristics tailored to particular translation pairs, making them difficult to generalize across diverse programming language combinations.”
  • The paper relies on this without support.

    Many programming language repositories contain configuration files and resource files.

    “Many programming language repositories contain configuration files and resource files, such as CMakeLists.txt for C++ and pom.xml for Java.”
  • The paper relies on this without support.

    A repository's star count above 50 indicates sufficient code quality and practical relevance.

    “To ensure repository quality, we rank repositories by star count and retain only those with more than 50 stars.”
  • The paper relies on this without support.

    The 21 surveyed professional developers' translation-pair requests represent real-world developer needs.

    “We receive responses from 21 professional developers, comprising 86 requests for specific translation pairs.”
  • The paper relies on this without support.

    Line and branch coverage metrics indicate high-quality test suites.

    “The coverage analysis ensures that our benchmark maintains high-quality standards, with our current dataset achieving an average of 81.89% line coverage and 72.61% branch coverage across all translation pairs as shown in Table II.”
  • The paper relies on this without support.

    The evaluated LLMs represent the current state-of-the-art.

    “our evaluation includes leading models from major providers (OpenAI, Anthropic, Google, Alibaba, DeepSeek) that represent the current state-of-the-art”
  • The paper relies on this without support.

    Large language models exhibit inherent randomness in their outputs.

    “Large language models exhibit inherent randomness in their outputs, which could affect the reproducibility of our results.”
  • The paper relies on this without support.

    Real-world test suites from production repositories provide more realistic evaluation scenarios compared to artificially constructed benchmarks.

    “Real-world test suites from production repositories provide more realistic evaluation scenarios compared to artificially constructed benchmarks.”
  • The paper relies on this without support.

    Successful repository-level translation tools should prioritize handling well-structured, maintainable codebases that represent common development scenarios.

    “as successful repository-level translation tools should prioritize handling well-structured, maintainable codebases that represent common development scenarios.”
  • The paper relies on this without support.

    Programming languages, frameworks, and development practices evolve continuously.

    “as programming languages, frameworks, and development practices evolve continuously.”
  • The paper relies on this without support.

    The inclusion of diverse language combinations provides insights into various translation scenarios encountered in practice.

    “The inclusion of diverse language combinations (e.g., C ↔ Python, Java ↔ Go, Python ↔ Rust) provides insights into various translation scenarios encountered in practice.”
12 of 12

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

Each contradiction between two passages listed here was confirmed by an independent check.

  • Gemini is classified as both open-source and closed-source

    Minor

    The results discussion lists Gemini among open-source alternatives, whereas the model-selection section explicitly places it among the closed-source LLMs.

  • Translation pairs involve nine distinct languages, not seven

    Minor

    The seven-language count matches the source languages, but the listed translation pairs also include Go and Rust as targets, making nine distinct languages involved in the benchmark.

  • Sample count does not surpass every previous benchmark

    Minor

    The claimed 1,897 samples do not surpass the 1,942 samples listed for the earlier xCodeEval benchmark.

3 of 3

Cites

Flagged first, then by citations

Cited by

Sorted by citations

Authors
Wang, Y., Wang, Y., Wang, S., Guo, D., Chen, J., Grundy, J., Liu, X., Ma, Y., Mao, M., Zhang, H., & Zheng, Z.
Affiliations
  • Sun Yat-sen University (CN)
  • Monash University (AU)
  • Huawei Technologies (China) (CN)
  • Chongqing University (CN)
Venue
IEEE Transactions on Software Engineering
Published
2026-02
Volume
52
Issue
2
Pages
675-690
ISSN
  • 0098-5589 (ISSN-L)
  • 1939-3520
  • 2326-3881
OpenAlex
W4417439109
Cited by
12
References
35
Citations by year
2026: 9 · 2025: 3
FWCI
13.11
Type
journal article
Language
en
Open access
Locations
  • IEEE Transactions on Software Engineering (publishedVersion)
  • arXiv (Cornell University) (submittedVersion)
  • arXiv (Cornell University)
Funders
CCF-Huawei Populus Grove Fund (CCF-HuaweiSE202403)
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Physical Sciences › Computer Science › Artificial Intelligence › Natural Language Processing Techniques
  • Physical Sciences › Computer Science › Artificial Intelligence › Topic Modeling
Keywords
large language models, test suite execution, error analysis

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Claims read by deepseek-v4.1-flash under definition version 3 (extract-v3) on 2026-10-16.

Classified by jev-1.13-20260917 (gold-guideline-v0.2) on 2026-10-16.

Cited sources are checked by gpt-6-sol.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review