Opportunity summary
Score5.0This canonical paper page includes Commercialization Proof and Related Resources.
ARXIV:2603.26567 · LLM EVALUATION · SUBMITTED 30 MAR · 21:57 UTC · FRESHNESS STALE
ARXIV:2603.26567LLM EVALUATIONSUBMITTED 30 MAR · 21:57 UTCFRESHNESS STALEYoseph Berhanu Alebachew · Hunter Leary · Swanand Vaishampayan · Chris Brown · arXiv
A new dataset and evaluation framework to benchmark LLMs on understanding entire code repositories, revealing limitations in current reasoning capabilities.
Opportunity summary
Pain A new dataset and evaluation framework to benchmark LLMs on understanding entire code repositories, revealing limitations in current reasoning capabilities.
Evidence 78 refs | 3 sources | 50% coverage
Blocker Evidence unverified
A new dataset and evaluation framework to benchmark LLMs on understanding entire code repositories, revealing limitations in current reasoning capabilities. However, most studies and benchmarks focus on isolated functions or single-file snippets, overlooking the…
Large Language Models (LLMs) have shown impressive capabilities across software engineering tasks, including question answering (QA). However, most studies and benchmarks focus on isolated functions or single-file snippets, overlooking the challenges of real-world program…
ScienceToStartup currently rates this 5.0/10 on the public viability pass. Our results show that LLMs achieve moderate accuracy at baseline, with performance improving when structural signals are incorporated. Code availability is flagged in the…
LLM Evaluation moved forward this cycle; last verified April 2026. Public score 5.0/10. Production flags indicate code availability.
Continue into Read for claims, analysis, references, and neighboring papers.
mobile layout uses overflow-hidden min-w-0 break-wordsOpportunity summary
Score5.0Analysis summary
A new dataset and evaluation framework to benchmark LLMs on understanding entire code repositories, revealing limitations in current reasoning capabilities.
Loading BUILD…
Paper Pack
10.48550/arXiv.2603.26567A new dataset and evaluation framework to benchmark LLMs on understanding entire code repositories, revealing limitations in current reasoning capabilities.
Abstract
Large Language Models (LLMs) have shown impressive capabilities across software engineering tasks, including question answering (QA). However, most studies and benchmarks focus on isolated functions or single-file snippets, overlooking the challenges of real-world program comprehension, which often spans multiple files and system-level dependencies. In this work, we introduce StackRepoQA, the first multi-project, repository-level question answering dataset constructed from 1,318 real developer questions and accepted answers across 134 open-source Java projects. Using this dataset, we systematically evaluate two widely used LLMs (Claude 3.5 Sonnet and GPT-4o) under both direct prompting and agentic configurations. We compare baseline performance with retrieval-augmented generation methods that leverage file-level retrieval and graph-based representations of structural dependencies. Our results show that LLMs achieve moderate accuracy at baseline, with performance improving when structural signals are incorporated. Nonetheless, overall accuracy remains limited for repository-scale comprehension. The analysis reveals that high scores often result from verbatim reproduction of Stack Overflow answers rather than genuine reasoning. To our knowledge, this is the first empirical study to provide such evidence in repository-level QA. We release StackRepoQA to encourage further research into benchmarks, evaluation protocols, and augmentation strategies that disentangle memorization from reasoning, advancing LLMs as reliable tool for repository-scale program comprehension.
Source availability
PDF linkedThe paper record includes a public PDF URL.
Extraction status
Parse run linkedA document parse run is attached to this paper.
Proof status
unverified78 refs; 3 sources; 50% coverage.
What was readable
Derived fallback: Estimated from adjacent evidence; not verified from source.
Viability
Time to MVP
Commercial
Export
Preparing verified analysis
Dimensions overall score 5.0
PROBLEM
A new dataset and evaluation framework to benchmark LLMs on understanding entire code repositories, revealing limitations in current reasoning capabilities. However, most studies and benchmarks focus on isolated functions or single-file snippets, overlooking the challenges of re...
METHOD
Large Language Models (LLMs) have shown impressive capabilities across software engineering tasks, including question answering (QA). However, most studies and benchmarks focus on isolated functions or single-file snippets, overlooking the challenges of real-world program compre...
RESULT
ScienceToStartup currently rates this 5.0/10 on the public viability pass. Our results show that LLMs achieve moderate accuracy at baseline, with performance improving when structural signals are incorporated. Code availability is flagged in the production record; the public rep...
WHY NOW
LLM Evaluation moved forward this cycle; last verified April 2026. Public score 5.0/10. Production flags indicate code availability.
In this work, we introduce StackRepoQA, the first multi-project, repository-level question answering dataset constructed from 1,318 real developer questions and accepted answers across 134 open-source Java projects.
This is explicitly stated in the abstract and introduction as a novel contribution.
partial
Our findings indicate that while LLMs achieve moderate accuracy (around58%) on repository-level QA, much of this success can be attributed to memorization of previously seen Stack Overflow content rather than genuine reasoning over source code.
This is a direct result reported in the abstract and further elaborated in the introduction.
partial
RAG provided measurable improvements, with graph-based retrieval yielding the largest gains; however, even the best configuration only increased accuracy to approximately64%.
The abstract and introduction highlight the effectiveness of graph-based RAG.
partial
The analysis reveals that high scores often result from verbatim reproduction of Stack Overflow answers rather than genuine reasoning.
This is a key finding explicitly stated in the abstract and supported by the ablation study description.
partial
We discuss key limitations of LLMs on repository-level tasks, such as performance degradation on unseen questions and sensitivity to irrelevant context
This limitation is mentioned in the abstract and further detailed in the 'Insights and Resources' section.
partial
In source-code RAG setups, retrieval solely based on flat textual similarity is insufficient, because code inherently encodes structural and semantic relationships—such as function calls, class hierarchies, and data-flow dependencies—that extend beyond what text similarity can capture [59].
This is a technical justification for the proposed graph-based approach, stated in the introduction.
partial
RAG provided measurable improvements, with graph-based retrieval yielding the largest gains; however, even the best configuration only increased accuracy to approximately64%.
This is a specific quantitative result reported in the abstract.
partial
In this work, we introduce StackRepoQA, the first multi-project, repository-level question answering dataset constructed from 1,318 real developer questions and accepted answers across 134 open-source Java projects.
This is explicitly stated in the abstract and introduction, highlighting its novelty and scope.
partial
Our findings indicate that while LLMs achieve moderate accuracy (around58%) on repository-level QA, much of this success can be attributed to memorization of previously seen Stack Overflow content rather than genuine reasoning over source code.
The abstract and analysis excerpt provide a specific percentage for baseline LLM accuracy.
partial
RAG provided measurable improvements, with graph-based retrieval yielding the largest gains; however, even the best configuration only increased accuracy to approximately64%.
The abstract and analysis excerpt state that RAG provides improvements, with graph-based retrieval yielding the largest gains.
partial
RAG provided measurable improvements, with graph-based retrieval yielding the largest gains; however, even the best configuration only increased accuracy to approximately64%.
The analysis excerpt provides a specific upper bound for accuracy with augmentation.
partial
Our results show that LLMs achieve moderate accuracy at baseline, with performance improving when structural signals are incorporated. Nonetheless, overall accuracy remains limited for repository-scale comprehension. The analysis reveals that high scores often result from verbatim reproduction of Stack Overflow answers rather than genuine reasoning.
This is a key finding explicitly stated in the abstract and analysis.
partial
Paper-native neighborhood for concepts, methods, materials, markets, and competitors. Missing lanes stay labeled instead of disappearing behind commercialization gates.
Concepts
Methods
Materials
Markets
Competitors
A new dataset and evaluation framework to benchmark LLMs on understanding entire code repositories, revealing limitations in current reasoning capabilities.
Segment
LLM Evaluation
Adoption evidence
No public code link in the paper record yet
Commercial read
5.0/10 public viability
Direct
Adjacent
Substitute
Unknown
No indexed public discussion is attached to 2603.26567 yet. That is a visibility signal, not a blank module: the monitor is watching the public channels below.
Hacker News
Not indexed yet
Not indexed yet
Bluesky
Not indexed yet
Preview the source document here, or use the hero PDF action for a new tab.
Reference metadata is not materialized in the public index yet. The source PDF remains the authority; cache refresh is optional.
CITED BY
No citing papers are indexed in the public S2S graph yet. This is an explicit zero-signal state, not a hidden lookup.
Foundation
Extension
Commercially relevant
Owned Distribution
Get the weekly shortlist of commercializable papers, benchmark movers, and proof receipts that matter for product execution.
3/3 checks · 100%
Build Passport
Build passport pending - Proof Lab budget No verified cost estimate / $7.00 cap
status
missing
reason
passport_row_missing
proof status
unverified
cost/budget
No verified cost estimate
confidence low
next verification path
Build brief missing until Build Passport data exists.
Source missing: Build Passport payload.
Experiment plan missing until prototype path is available.
No prototype path attached.
Validation checklist missing until required assets, cost, and regulatory flags are verified.
No checklist artifact is attached to the Build Passport payload.
Derived signals show verified:false until source-backed receipts exist.
Evidence coverage
OpportunityKernel evidence_receipt
78 refs / 3 sources / 50% coverage
stale
Verify missing sources before using this as buyer proof. verified:false
Build readiness
BuildPassport EvidenceState
passport absent
stale
Run Proof Lab or inspect typed missing state. verified:false
Artifact maturity
GitHub and Hugging Face maturity payloads
No public artifact surface observed
stale
Open source artifacts or mark the gap as missing. verified:false
Technical feasibility
partial
Current read
Runnable path is not fully verified.
Evidence
No Build Passport payload attached.
Gaps
Next test
Run minimal reproduction from the Build Passport prototype path.
Market urgency
partial
Current read
Research evidence exists; buyer urgency still needs source proof.
Evidence
78 references, 3 sources, 50% evidence coverage.
Gaps
Next test
Collect buyer interview, deployment evidence, or cited demand signal.
Buyer clarity
missing
Current read
No budget owner is verified for this paper.
Evidence
Build tab has no CRM, procurement, or operator source.
Gaps
Next test
Map target operator, economic buyer, and procurement trigger.
Defensibility
missing
Current read
Defensibility signals are missing.
Evidence
No defensibility receipt attached.
Gaps
Next test
Refresh defensibility bars with source receipts.
Integration burden
missing
Current read
No public implementation surface observed.
Evidence
No GitHub or Hugging Face payload attached.
Gaps
Next test
Write integration checklist from prototype path and target workflow.
Capital intensity
missing
Current read
No observed cost estimate is verified.
Evidence
Cost passport has no observed_usd value.
Gaps
Next test
Run cost passport or mark the cost field not applicable.
Regulatory load
missing
Current read
No regulatory classification is attached.
Evidence
Build Passport ledger does not include regulatory flags.
Gaps
Next test
Classify regulatory flags before commercialization planning.
No named scientific founder assigned.
Paper authors are not treated as operators without consent.
People
No named person assigned.
Gaps
Next verification path
Prototype owner missing.
Build Passport does not name an implementer.
People
No named person assigned.
Gaps
Next verification path
Operator workflow not sourced.
No buyer or workflow interview attached.
People
No named person assigned.
Gaps
Next verification path
No GTM owner verified.
No CRM or outreach source attached.
People
No named person assigned.
Gaps
Next verification path
Regulatory need unclassified.
No clinical or regulatory source attached.
People
No named person assigned.
Gaps
Next verification path
ARTIFACTS
No public artifacts yet.
DEFENSIBILITY
Defensibility and confidence evidence pending.
WATCHTOWER
No verified watchtower monitor rows yet.
FORESIGHT
No prediction yet — minted on next Foresight batch.
OPPORTUNITYKERNEL CHANGES SINCE LAST VIEW
No verified OpportunityKernel changes since the last view.
COMPETITIVE LANDSCAPE UPDATES
No verified competitive landscape changes yet.
RELATED PAPER UPDATES
No verified related paper changes yet.
SIGNAL CANVAS HISTORY AND DELTAS
No Signal Canvas history deltas yet.
TIMELINE
Save this paper to start tracking momentum - commits, demos, and score changes appear here.
No tracked events yet.
Score trend will appear after multiple data points.
BUZZ
Buzz trend pending.