This release is a pre-release and may not be stable for production use.
ssebench-sdk
The Python SDK of SSEBench, a
benchmark that measures how well AI coding agents fix real security
vulnerabilities. It is imported as sse.
Code that runs inside an SSEBench task container uses the SDK: an agent reads
the task and checks its patch with the build, test and proof-of-concept
actions, and the evaluator grades the result. The SDK is a client of
ssebench-daemon, which serves those actions over the Unix socket named by the
SSE_DAEMON_SOCKET environment variable. It does nothing useful outside a task
container.
Install
pip install ssebench-sdk==<version>
Use the version of the SSEBench release you run against; see
Versions. The SDK needs Python 3.12 or newer. An agent that runs in
a task container installs it into its own environment; the reference agent in
the SSEBench repository, agents/reference, is the smallest example.
Use
from sse import project
print(project.metadata.id, project.source)
result = project.build()
if result.is_success():
print(project.function_test().stdout)
import sse does not contact the daemon. sse.project and sse.prompt ask it
for the task when they are imported, so import them only inside a task
container.
Versions
SSEBench components share one version and are released together, so
ssebench-sdk X is made for ssebench-daemon X. Install the SDK version
that matches the SSEBench release whose task container your code runs in, for
example by pinning ssebench-sdk==X. When the SDK connects, it reads the
daemon's version from GET /version and logs a warning if the two differ. The
warning does not stop your code, but the two may disagree about the API, so
treat it as a sign to fix the pin.
sse.__version__ holds the SDK's version. SSEBench writes the same version as
1.2.0-rc.1 in VERSION and in the daemon, and as 1.2.0rc1 in Python
packages; they name the same release.
Documentation
The SDK is licensed under the Apache License 2.0.
Metadata
Release files for ssebench-sdk 1.0.0rc1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ssebench_sdk-1.0.0rc1.tar.gz | 27.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ssebench_sdk-1.0.0rc1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 53.6 kB
Release files / ssebench_sdk-1.0.0rc1.tar.gz
| Download URL | ssebench_sdk-1.0.0rc1.tar.gz |
|---|---|
| Size | 27.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8ca92cf73bf824e6ca1ecc89468bb304327d3b84bcf205852e5d16b337f76fae
|
|
BLAKE2b-256 checksum How to use checksums |
e7f75453171c72cda4af6bc99afbb1ea1aa6bfbb5f0ac9a8fc31cf59f3be5228
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / ssebench_sdk-1.0.0rc1-py3-none-any.whl
| Download URL | ssebench_sdk-1.0.0rc1-py3-none-any.whl |
|---|---|
| Size | 26.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a57708f4b1ad67b279631e6d3c2b9cd87fd8c5cc35a3e5585fd2cb413571dffd
|
|
BLAKE2b-256 checksum How to use checksums |
66f6cf7f11458332d91fa3da01748b73bff5f7f13721c0ee7312486a5bd0cc4f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency log