SourceScore

Verified claim · AI-ML · 100% confidence

SWE-bench introduced in: Jimenez et al. 2024 — software engineering benchmark from GitHub issues.

Last verified 2026-05-16 · Methodology veritas-v0.1 · b16b5f5297e5f621

SourceScore rates how reliable a source is to cite — for AI answers and research. This is one verified claim from the catalog.

Related verified claims

More verified claims related to this one — keep exploring.

Structured fields

Subject
SWE-bench
Predicate
introduced_in
Object
Jimenez et al. 2024 — software engineering benchmark from GitHub issues
Confidence
100%
Tags
swe-bench · princeton · benchmark · coding · evaluation · introduced_in · 2023

Sources (2)

  1. [1] preprint · arXiv (Jimenez, Yang, Wettig, Yao, Pei, Press, Narasimhan / Princeton + Chicago) · 2023-10-10

    SWE-bench: Can Language Models Resolve Real-World GitHub Issues?
    “Language models have outpaced our ability to evaluate them effectively, but for their future development it is essential to study the frontier of their capabilities. We find real-world software engineering to be a rich, sustainable, and challenging testbed.”
  2. [2] official blog · SWE-bench team · 2024-01-01

    SWE-bench — official benchmark site

Cite this claim

Ready-to-paste citation (Markdown / plain text):

SWE-bench introduced in: Jimenez et al. 2024 — software engineering benchmark from GitHub issues. — SourceScore Claim b16b5f5297e5f621 (verified 2026-05-16). https://sourcescore.org/api/v1/claims/b16b5f5297e5f621.json

Embed this claim

Drop this iframe into any blog post, docs page, or knowledge base. The widget renders the claim record + top cited source + click-through to this canonical page. CC-BY 4.0; attribution included.

<iframe src="https://sourcescore.org/embed/claim/b16b5f5297e5f621/" width="100%" height="360" frameborder="0" loading="lazy" title="SWE-bench introduced in: Jimenez et al. 2024 — software engineering benchmark from GitHub issues."></iframe>

Preview: open in new tab

Frequently asked questions

How has SourceScore reviewed the claim "SWE-bench introduced in: Jimenez et al. 2024 — software engineering benchmark from GitHub issues."?

SourceScore records this assertion with 100% legacy editorial confidence as of 2026-05-16, under methodology veritas-v0.1. That metadata is not a truth guarantee. Inspect the 2 cited source record(s), excerpts, and live evidence below.

What is the evidence for "SWE-bench introduced in: Jimenez et al. 2024 — software engineering benchmark from GitHub issues."?

The record lists 2 cited source(s): arXiv (Jimenez, Yang, Wettig, Yao, Pei, Press, Narasimhan / Princeton + Chicago), SWE-bench team. Each is shown below with a short excerpt and URL. The JSON record at https://sourcescore.org/api/v1/claims/b16b5f5297e5f621.json includes SourceScore-issued HMAC integrity metadata, not a public verification proof.

When was this claim record last reviewed by SourceScore?

Last reviewed 2026-05-16 under methodology version veritas-v0.1. The dated JSON record includes SourceScore-issued HMAC metadata, which is not publicly recomputable. Refetch the record and inspect current evidence before relying on it.

How can I cite this SourceScore claim in my code or article?

Fetch the JSON record from https://sourcescore.org/api/v1/claims/b16b5f5297e5f621.json, including the verbatim claim, cited evidence, confidence, methodology version, and last-verified date. Refetch the canonical HTTPS record and inspect cited evidence; the HMAC tag is not publicly independently verifiable. The CC-BY-4.0 license permits commercial use with attribution to SourceScore.

Use this claim in your code

Fetch this record from your application. The response includes verbatim excerpts, primary-source URLs, and SourceScore-issued HMAC integrity metadata. Refetch the canonical HTTPS record and inspect cited evidence; public users cannot independently verify the HMAC tag.

cURL

curl https://sourcescore.org/api/v1/claims/b16b5f5297e5f621.json

JavaScript / TypeScript

const r = await fetch("https://sourcescore.org/api/v1/claims/b16b5f5297e5f621.json"); const envelope = await r.json(); console.log(envelope.claim.statement); // "SWE-bench introduced in: Jimenez et al. 2024 — software engineering benchmark from GitHub issues."

Python

import httpx r = httpx.get("https://sourcescore.org/api/v1/claims/b16b5f5297e5f621.json") envelope = r.json() print(envelope["claim"]["statement"]) # "SWE-bench introduced in: Jimenez et al. 2024 — software engineering benchmark from GitHub issues."

LangChain (retrieve-then-cite)

from langchain_core.tools import tool import httpx @tool def get_swe_bench_fact() -> dict: """Fetch the verified SourceScore claim for SWE-bench.""" r = httpx.get("https://sourcescore.org/api/v1/claims/b16b5f5297e5f621.json") return r.json()
Sister toolIs your own site ready to be cited by AI? CitationDesk audits the page signals that help ChatGPT, Claude, Perplexity & Gemini cite you — get your free AI Visibility Score →