Repo brief: locustio/locust

Generated by RepoPilot · document generated 2026-09-17 · concise human review Evidence snapshot · analyzed 2026-09-17T03:59:22.502Z · commit f391a716e12c

Verdict

Healthy — Strong maintenance signals

• Last commit 3d ago
• 10 active contributors
• MIT licensed
• CI configured
• 1 more receipt on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard

What it is

Locust is an open-source load testing framework that lets developers write performance tests in plain Python instead of domain-specific languages or GUIs. It simulates thousands of concurrent users via gevent greenlets and supports distributed testing across multiple machines, with results viewable in a real-time web UI or exported for analysis. Core capability: protocol-agnostic load testing (HTTP, MQTT, MongoDB, PostgreSQL, Socket.IO, etc.) through pluggable contrib modules. Hybrid monorepo: Python core in locust/ (user models, runners, stats, RPC protocol), with pluggable contrib modules for different protocols; locust/webui/ is a separate TypeScript/React/Redux app bundled into the…

Start here

Open these first:

• locust/main.py — Entry point orchestrating the load test lifecycle, runner initialization, and web UI or CLI mode selection.
• locust/env.py — Environment singleton managing test configuration, event hooks, and shared state across distributed workers.
• locust/runners.py — Core Runner classes (SequentialRunner, MasterRunner, WorkerRunner) controlling test execution, spawning, and synchronization.
• locust/user/users.py — Base HttpUser and User classes defining task execution, wait times, and behavioral patterns for load test clients.
• locust/stats.py — Statistics aggregation engine tracking response times, failures, throughput, and generating real-time or export metrics.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

Clone and install: git clone https://github.com/locustio/locust.git && cd locust. Install dependencies via pip (verify setup.py or pyproject.toml in repo root for exact requirements). For webui development: `cd lo…

Daily commands:

Backend: locust -f locustfile.py --web (starts UI on http://localhost:8089). Distributed: locust -f locustfile.py --master on coordinator + locust -f locustfile.py --worker --master-host=<ip> on worker nodes. Fron…

…shortened for this brief.

Key cautions & unknowns

• Concentrated ownership — top contributor handles 67% of recent commits
• Scorecard: dangerous CI workflow (0/10)
• Greenlet limits: Single process can handle 10k+ concurrent users but CPU-bound test logic will saturate; distributed mode required for linear scaling. ZMQ firewall: Distributed mode requires open TCP ports…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests
• OpenSSF Scorecard

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.