IssueBenchKit
Turn a real GitHub issue, pull request, or local bug into a small coding-agent benchmark task.
SWE-bench is great when you want a public leaderboard. Most teams need something smaller: a repeatable task built from the bugs they actually care about, with a clear test command and a report that says whether a candidate patch really fixed it.
IssueBenchKit is that local builder. It does not try to invent tests for you. It packages the issue context, base commit, reproduction command, and scoring result so you can evaluate coding agents on your own repositories.
Quick Start
pip install issuebenchkit
Create a benchmark task:
issuebench init tasks/qwen-copy \
--repo ./qwen-code \
--issue https://github.com/QwenLM/qwen-code/issues/4716 \
--base 8b4f3b2 \
--test "npm test -- copyCommand.test.ts"
Run the task against a candidate checkout:
issuebench run tasks/qwen-copy --repo ./candidate-qwen-code --out after.json
Compare before and after:
issuebench score tasks/qwen-copy --before before.json --after after.json
Export a report:
issuebench export tasks/qwen-copy --format html --out report.html
What It Stores
Each task directory contains one issuebench.json manifest:
- source repo path and optional GitHub issue URL
- base commit or version marker
- reproduction / validation command
- expected signal, notes, and tags
Run results are plain JSON files with exit code, duration, command, stdout tail, stderr tail, and the pass/fail verdict. They are easy to archive, diff, or attach to a PR.
Why Not Just Use SWE-bench?
Use SWE-bench for public comparison. Use IssueBenchKit when you need:
- a benchmark task for a private or small repo
- a tiny task that can run in CI
- a before/after report for one real bug
- a dataset of issues that reflects your own engineering workflow
Current Scope
The first version is intentionally small:
- generic shell test commands
- JSON manifest files
- before/after scoring
- JSONL and single-file HTML export
It does not generate tests automatically, mutate repositories, or claim that one command can evaluate every language ecosystem.
License
MIT
Metadata
Release files for issuebenchkit 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| issuebenchkit-0.1.0.tar.gz | 9.7 kB | With provenance | Details for issuebenchkit-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| issuebenchkit-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for issuebenchkit-0.1.0-py3-none-any.whl |
Total release size: 19.7 kB
Release files / issuebenchkit-0.1.0.tar.gz
| Download URL | issuebenchkit-0.1.0.tar.gz |
|---|---|
| Size | 9.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e16718584f69f1b8256ec75030d669b5f65626dc7b2413d15c21fb1ac5bb1de9
|
|
BLAKE2b-256 checksum How to use checksums |
a33e1c26e39d7ed611a5c1dc8b9fe00a33a835483e9c06ff00b2410702033493
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 4, 2026.
Transparency logRelease files / issuebenchkit-0.1.0-py3-none-any.whl
| Download URL | issuebenchkit-0.1.0-py3-none-any.whl |
|---|---|
| Size | 10.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2f5eea95d19b9b7f0887f620b42f19f3ecad75cdde2bf11e17df905038fc128a
|
|
BLAKE2b-256 checksum How to use checksums |
876b5d7ef923ebd6efa38c6bbe7b54d823d7bcf01879011815d2e3ba66e047eb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 4, 2026.
Transparency logSecurity for issuebenchkit 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for issuebenchkit-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 4, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.