Welcome to Inspect SWE, a suite of software engineering agents for Inspect AI.
For details on using Inspect SWE, please visit https://meridianlabs-ai.github.io/inspect_swe/.
Installation
Latest development version:
pip install git+https://github.com/meridianlabs-ai/inspect_swe
Development
To work on development of Inspect SWE, clone the repository and install it with uv (0.13.4 or later) and the [dev] optional dependencies:
git clone https://github.com/meridianlabs-ai/inspect_swe
cd inspect_swe
uv sync --locked --extra dev
To build the docs, run uv sync --locked --extra dev --extra doc instead.
Run the commands below from the .venv that uv sync creates: uv run <command>, .venv/bin/<command>, or source .venv/bin/activate.
Run linting, formatting, and tests via
make check
make test
Sandbox-specific tests
Note that most tests depend on a valid sandbox being available (either docker or k8s), this is inferred from your shell environment.
You can check which are collected via pytest --co
1 maintainer
Metadata
1 maintainer
Release files for inspect-swe 0.3.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 |
|---|---|---|---|---|
| inspect_swe-0.3.0.tar.gz | 198.4 kB | With provenance | Details for inspect_swe-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| inspect_swe-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for inspect_swe-0.3.0-py3-none-any.whl |
Total release size: 437.4 kB
Release files / inspect_swe-0.3.0.tar.gz
| Download URL | inspect_swe-0.3.0.tar.gz |
|---|---|
| Size | 198.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6304e3a9f92f8307cdf0b7f87ef0a7b5c318f3c1b2fa5492da9bb716d8c2b8c6
|
|
BLAKE2b-256 checksum How to use checksums |
5b0b2f0ca2d91b3b57a62265840cc1895f87166ce81c02033d76904f211bf2eb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 12, 2026.
Transparency logRelease files / inspect_swe-0.3.0-py3-none-any.whl
| Download URL | inspect_swe-0.3.0-py3-none-any.whl |
|---|---|
| Size | 239.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
94276e6642a9e63565824e449a0a2a6e8057ff17c282307fd60d2935d8d010b7
|
|
BLAKE2b-256 checksum How to use checksums |
146e8a68c6036d778e0fa2e4911055f71d91f0b472faf07fe5dc11ce70390024
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 12, 2026.
Transparency logSecurity for inspect-swe 0.3.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 inspect_swe-0.3.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 Nov 12, 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.
