Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

Prime Intellect


Overview

verifiers is our library for creating environments to train and evaluate LLMs.

verifiers is tightly integrated with the Environments Hub, as well as our training framework prime-rl and our Hosted Training platform.

Installation

We recommend installing the Prime CLI to interact with the environments.

# install uv
curl -LsSf https://astral.sh/uv/install.sh | sh
# install the prime CLI
uv tool install prime

Further reading

  • The docs contain short, human-written guides and overviews about the architecture.
  • The AGENTS.md and skills are for coding agents and go into more details.

Contributing

We welcome community contributions. We use issues to track bugs and feature requests. If you hit a bug, a pain point, or have an idea for a feature, please open an issue.

Contributions are welcome via PR. Please follow these guidelines:

  1. Install the pre-commit hooks so your code is formatted and type-checked.
  2. Keep your PR in "Draft" until it is ready for review.
  3. If your PR resolves an issue, link the issue in the PR description.
  4. Run the tests for the areas you touched.

Pre-commit hooks

uv run pre-commit install

Tests

Unit tests run one component in isolation, with no network, and mirror the verifiers/v1 layout. Integration tests run real evals: they need PRIME_API_KEY and skip without it.

uv run pytest tests/unit -n auto                       # unit
uv run pytest tests/integration -n 8                   # integration
uv run pytest tests/integration/test_single_turn.py    # one behavior
uv run pytest tests/integration -m "docker and codex"  # one runtime and harness

Citation

Originally created by Will Brown (@willccbb).

@misc{brown_verifiers_2025,
  author       = {William Brown},
  title        = {{Verifiers}: Environments for LLM Reinforcement Learning},
  howpublished = {\url{https://github.com/PrimeIntellect-ai/verifiers}},
  year         = {2025}
}

Metadata

Release files for verifiers 0.4.1.dev137

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for verifiers 0.4.1.dev137
File Size Uploaded Provenance Actions
verifiers-0.4.1.dev137.tar.gz 506.4 kB With provenance Details for verifiers-0.4.1.dev137.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for verifiers 0.4.1.dev137
File Interpreter ABI Platform Actions
verifiers-0.4.1.dev137-py3-none-any.whl Python 3 none any Details for verifiers-0.4.1.dev137-py3-none-any.whl

Total release size: 1.0 MB

Release files / verifiers-0.4.1.dev137.tar.gz

Download URL verifiers-0.4.1.dev137.tar.gz
Size 506.4 kB
Tags Source
SHA-256 checksum
How to use checksums
4dd0233b38e5027454ade48678a984e6a35dad1ecb070418b60278baa1e039f2
BLAKE2b-256 checksum
How to use checksums
9476a758bd7d02c3517008c2da98c129139e6d24fd9b271fb8d2856320a215ad
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 Nov 2, 2026.

Transparency log

Release files / verifiers-0.4.1.dev137-py3-none-any.whl

Download URL verifiers-0.4.1.dev137-py3-none-any.whl
Size 534.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
18ced264aac0634fefe3bebdfc63385c21024660f2799d36da6ad4a5a08b0a2e
BLAKE2b-256 checksum
How to use checksums
466f3392632a5e80acf530fd2263695c8a4d02bf4102479a0ac175d68ab6e0b9
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 Nov 2, 2026.

Transparency log

Security for verifiers 0.4.1.dev137

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

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for verifiers-0.4.1.dev137.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 2, 2026.

Transparency log

A 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.

Release history Release notifications | RSS feed

This release
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page