# SWT-bench Lite leaderboard

external benchmark

> Every figure below is reproduced as its upstream source published it: nothing is modelled, estimated, interpolated or converted. `Unavailable` means no source published the value — it is never a zero. Each value carries its evidence state and the date it was observed.

Page: https://modelscale.dev/leaderboards/benchmarks/external-swt-bench-lite

SWT-bench Lite (276 issues from SWE-bench Lite). Every model the catalog carries a published SWT-bench Lite value for, ranked by that value.

## Benchmark record

| Field | Value |
| --- | --- |
| Category | external |
| Measure | Agent or model gets the issue and the pre-fix repository and adds tests; tests run before and after the reference fix |
| Tasks | 276 GitHub issues from SWE-bench Lite (Python repositories) |
| Difficulty | Reproducing a bug from an issue report as a failing test |
| Published by | [SWT-Bench: Testing and Validating Real-World Bug-Fixes with Code Agents](https://arxiv.org/abs/2406.12952) |

The smaller SWT-bench split: 276 GitHub issues from SWE-bench Lite, scored the same way as Verified by the share of issues whose generated tests fail on the original code and pass after the fix.

## SWT-bench Lite ranking

No model in the catalog has a published SWT-bench Lite score. The benchmark is defined by SWT-Bench: Testing and Validating Real-World Bug-Fixes with Code Agents, but the catalog carries no value for it yet. An absent value is shown as absent here rather than as a zero.

Rows are ordered by the value the source published, highest first. The source does not state whether a higher value is the better result, so this document does not either: for a benchmark that measures a rate of failure, read the table from the bottom.
