Datasets:
Release information
CrossSWE-Bench contains 171 instances with 350 repository entries across 165 upstream repositories. The source material release is pinned to commit f447522ef369e721b1dbbfa28e53fa2c877e61cd.
Environments and evaluation
Each instance has a digest-pinned linux/amd64 image, repository definitions, task-specific test materials and evaluation metadata. Public tests run against the provided sources and ordinary dependencies. Candidate evaluation uses the separate entry point and contract listed in the evaluation directory.
The available validation records cover task-related public tests, source edits and rebuilds, source/Git/cache and image-layer checks, image identities, and initial/reference test outcomes. The records describe the recorded image and input versions; downloading this release does not run those tests again.
Some initial implementations fail during compilation or import because they lack the interface requested by the task. Other selected cases can remain unreached after an earlier failure. These records are separate from executed test failures, passes and skips. Preserve that distinction when interpreting results.
For example, Deno28946 records 142 passing initial cases and two unexecuted selections associated with compilation diagnostics; its reference implementation records 144 passing cases. Per-instance records retain the corresponding native test identities and result granularity.
Image access and reconstruction
Images target linux/amd64 and require authorized Docker Hub access. Their immutable references are listed in data/images.jsonl. Follow the selected environment's instructions for public tests and reconstruction; build layouts vary by instance.
Registry manifests, configuration and layer identities were checked during delivery. Independent OCI archive restoration coverage varies by instance; consult the per-instance records. Rebuilt images can have different metadata and digests from the published image.
Source and reference records
Gold and test artifacts retain their hash bindings. Source and exported task/contract hashes are recorded in data/task-bindings.jsonl. Some images use documented source projections or reference corrections; consult the data format and the selected environment's metadata to reproduce the supplied source tree and reference endpoint.
License texts, attribution and scope records are included under licenses/, with the complete inventory in upstream_licenses.csv. Those records retain their documented permission limits and unresolved scopes.