CrowdBench
CrowdBench measures local language models and contributes intelligence, speed and memory results to https://crowdbench.ai. The open-source runner is being prepared for the crowdbench 1.0 package. It is currently published as crowdbench-run; the package and command rename to crowdbench is coming.
Install and run CrowdBench with uv:
uvx --python 3.14 crowdbench-run
The guided wizard finds local engines, helps select a model and measurements, and asks for the required agreements before model work and uploads. The runner requires Python 3.14 or later; uv can obtain it. Use uvx --python 3.14 crowdbench-run --help for commands, uvx --python 3.14 crowdbench-run detect for serving engines and models, and uvx --python 3.14 crowdbench-run run --help for explicit benchmark options.
Linux, macOS and Windows are supported, with suite-specific limits. Native Windows does not support lm-eval code-execution suites, EvalPlus, or stock math scorers requiring signal.SIGALRM. WSL2 supports intelligence measurements, but public speed and memory measurements are unavailable. HTTP adapters include Ollama, llama.cpp, ik_llama.cpp, LM Studio, mlx-lm, oMLX, vLLM, LocalAI and Strata; suite capabilities and model evidence are still required. Isolated CrowdBench Engine runtimes use local MLX weights on Apple-silicon macOS or GGUF weights on compatible hosts with supported native wheels. Generative suites in the GGUF runtime are currently refused, including local-only runs.
Before running a model, the runner checks that you have accepted the current Terms of Service, even for work kept local. Uploading also requires agreement to the current Contribution Terms. One prompt can cover both agreements; --agree-tos records a human's acceptance in scripted use. Checks that execute generated code ask for another permission, supplied with --allow-code-exec on each scripted run. lm-eval's evaluator does not isolate that code from your machine.
Contributions can send scores, speed readings, harness result files, and full validation answers with reasoning and item timings. Full public-suite responses and reasoning are uploaded for private rescoring and audits rather than public display. Uploads also describe hardware, operating systems and run conditions, machine ownership or rental status and provider, engine configuration, setup answers and engine errors, model names, file metadata and fingerprints, the runner version and the recorded legal and code-execution acceptances. Session plans, skips and refusals with reason codes, and answer-length totals are sent too. During a check, periodic messages identify your contributor key and the active check, with request counts when available; they contain neither answers nor unfinished results.
The upload filters aim to omit direct identifiers such as your name, email, hostname, IP address and device serials. They also shorten recognized paths and mask recognized credentials, but filtering is incomplete: model responses, file metadata, copied names and engine errors can still expose personal information or secrets. A public contributor ID connects submissions made with the same key; the absence of an account name does not make those submissions anonymous.
This is an overview. Read the Privacy Policy for the exact privacy text, and run crowdbench-run --explain terms for the exact bundled agreements.
The runner fingerprints model weights and records configuration, harness and dataset evidence; missing observations stay unknown. Industry suites use their named harness and scoring rules. lm-eval's GSM8K extractor can score a correct answer wrong, and its MBPP+ suite checks the single shown assertion rather than EvalPlus's extended tests. Server checks remain separate; an upload receipt is not final acceptance. Submitted measurements can contain errors or deliberate manipulation; these checks do not independently verify every result. The source distribution includes the public README and design guides explaining these limits.
To contribute code, run uv run --extra dev pytest from the runner source directory. Send security reports through SECURITY.md.
Apache-2.0 · © 2026 Hooch Labs LLC
Metadata
Release files for crowdbench-run 0.1.208
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 |
|---|---|---|---|---|
| crowdbench_run-0.1.208.tar.gz | 7.7 MB | With provenance | Details for crowdbench_run-0.1.208.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| crowdbench_run-0.1.208-py3-none-any.whl | Python 3 | none | any | Details for crowdbench_run-0.1.208-py3-none-any.whl |
Total release size: 11.0 MB
Release files / crowdbench_run-0.1.208.tar.gz
| Download URL | crowdbench_run-0.1.208.tar.gz |
|---|---|
| Size | 7.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a8d1d271b92602d9cc67eeb2ca32f12a1a99a6ec87a7ac77cbbbdb0a77113328
|
|
BLAKE2b-256 checksum How to use checksums |
726c42a1eecd65d5d511dc930df4f7a2c7c22aaabcdca6f0a1f963c4e3c12355
|
| 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 Oct 30, 2026.
Transparency logRelease files / crowdbench_run-0.1.208-py3-none-any.whl
| Download URL | crowdbench_run-0.1.208-py3-none-any.whl |
|---|---|
| Size | 3.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d4952380475c4d1c9d2c74364bfb478829e5d6a96fabd1c8a187746b3d79eb36
|
|
BLAKE2b-256 checksum How to use checksums |
1648affd67dd6d074e203b7f5e44dfa83da77f55c3bbd92c899be988fc263547
|
| 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 Oct 30, 2026.
Transparency logSecurity for crowdbench-run 0.1.208
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.
Attestation for crowdbench_run-0.1.208.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 Oct 30, 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.