Martian SDK
One Python SDK for agent evaluations and adversarial testing.
martian.evals: pinned datasets, local MLflow evaluation, Backend-scored regression gates and recorded CI sessions.martian.redteam: adversarial probes against a customer callback, with simulation and judging through the Martian Backend API.assert_redteam(...): record saved adversarial probe results alongside dataset and quality checks in one eval session.martian ci: one persisted session for evals, redteam, or both, with typed Python results.
The distribution is martian-sdk; install its evals extra for both modules.
Use an available PyPI release or a validated wheel. Hosted use requires
compatible Backend SDK APIs and authorized tenant credentials.
uv sync --locked --extra evals
uv run --extra evals martian --help
uv run --extra evals martian redteam validate examples/config.yaml
# In the customer checkout, after configuring the Backend origin and one Martian API token:
martian ci --evals-path tests/evals --redteam-config redteam.yaml --output results
Unified SDK and CI documents imports, the shared connection, installation, the combined gate, compatibility and rollout limits. Documentation index covers the existing redteam contracts.
The wheel retains martian_redteam, martian_evals_kit and martian-redteam
for existing integrations. Both test engines run in the customer's process.
The Backend admits and stores customer work; Agents owns redteam simulation and judging.
The same Backend API key authorizes both modules when granted the required capabilities.
Development
uv sync --locked --extra evals
uv run --extra evals ruff format --check src tests examples
uv run --extra evals ruff check src tests examples
uv run --extra mcp --extra evals mypy src
uv run --extra evals pytest -q
uv build
The existing eval regression suite has moved into this SDK's CI. Tests use local MLflow and loopback service fixtures; hosted/paid execution is a separate qualification. See development.
License
1 maintainer
Metadata
1 maintainer
Release files for martian-sdk 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 |
|---|---|---|---|---|
| martian_sdk-0.1.0.tar.gz | 270.0 kB | With provenance | Details for martian_sdk-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| martian_sdk-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for martian_sdk-0.1.0-py3-none-any.whl |
Total release size: 359.2 kB
Release files / martian_sdk-0.1.0.tar.gz
| Download URL | martian_sdk-0.1.0.tar.gz |
|---|---|
| Size | 270.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
89465de5ec5eabd0a2305d2a3072acf6af3b914eeab64354a9e5e74caf59f84b
|
|
BLAKE2b-256 checksum How to use checksums |
902e99d8ec7e947e61caa140f065538dd66d3d758fea8da362d3176d8e74f174
|
| 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 6, 2026.
Transparency logRelease files / martian_sdk-0.1.0-py3-none-any.whl
| Download URL | martian_sdk-0.1.0-py3-none-any.whl |
|---|---|
| Size | 89.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b06a7c675c4795f76cde19e4a8fa1e0116dd8f5a70485d8aa31eb8254b129f14
|
|
BLAKE2b-256 checksum How to use checksums |
ce5d5fd84b6883855fef998facdf81212334009f40e8ac9df9801667b9e66580
|
| 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 6, 2026.
Transparency logSecurity for martian-sdk 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 martian_sdk-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 Nov 6, 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.
