locustio/locust
Write scalable load tests in plain Python 🚗💨
28.2k stars · 3.3k forks · Python
Healthy
Healthy: actively maintained by 19 people, no known risks.
Why
No rule fired.
What would change this
- Partly checked: maintenance (Commit counts are estimated: the commit sample stops before the window start, so GitHub's totals were scaled by the sampled bot share.)
- A dormant maintenance status, a deprecated or archived package, a successor link, or a critical advisory would change this.
Maintenance
PartialActive
- Human commits, 30 days
- 57
- Human commits, 90 days
- 137
- Human commits, 365 days
- 537
- Bot share of commits, 365 days
- 8%
- Last commit
- Oct 11, 2026 (3 days ago)
- Last human commit
- Oct 11, 2026 (3 days ago)
- Authors, 90 days
- 19
- Last release
- Oct 4, 2026 (10 days ago)
- Median PR merge time
- 14 hours
Responsiveness: of 13 recent issues, 100% got a maintainer reply. Median first response: 26 hours.
- Commit counts are estimated: the commit sample stops before the window start, so GitHub's totals were scaled by the sampled bot share.
Sources: Commits, Releases, Merged pull requests, Issues
People
Complete- Owner
- Organization
- Commits sampled
- 458 since Oct 14, 2025
- Authors for half of commits
- 1
- Authors for 80% of commits
- 5
- Contributors
- 329
Top committers
- cyberw: 64% of commits
- Amadeu Pereira: 9% of commits
- SulimanAbdulrazzaq: 3% of commits
- reachsridhard: 3% of commits
- andrewbaldwin44: 2% of commits
- Shares come from the newest sampled commits, since the commit sample is capped.
Sources: Commits, Contributors
Stars
CompleteOrganic, confidence high
Bursts
- Apr 18, 2014 to Apr 22, 2014: about 75 more stars than usual, peak 37 in one day, a spike that tapers off. No outside explanation found, so this burst is unexplained.
- Feb 12, 2015 to Feb 13, 2015: about 62 more stars than usual, peak 53 in one day, a spike that tapers off. No outside explanation found, so this burst is unexplained.
- Jul 1, 2015 to Jul 3, 2015: about 503 more stars than usual, peak 387 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Jan 11, 2016 to Jan 13, 2016: about 55 more stars than usual, peak 29 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Jun 5, 2020 to Jun 5, 2020: about 66 more stars than usual, peak 74 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Jan 5, 2021 to Jan 8, 2021: about 166 more stars than usual, peak 102 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Jan 14, 2021 to Jan 15, 2021: about 117 more stars than usual, peak 82 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- 132 stars on a repo created before February 2013 have no date, so they aren't in the chart.
Anyone can buy stars for any repo; bursts alone don't prove the owner did.
- The star history looks organic.
- 132 stars on the creation day are undated (before 2013-02-10) and are not counted.
Sources: How star history is analyzed
Risk
CompleteFlags
No risk flags.
License
- Now
- MIT (OSI-approved)
- A year ago
- MIT (OSI-approved)
Packages
- locust (PYPI): latest 2.46.8.dev24, published Oct 10, 2026
Advisories for the latest version: none listed
Package and advisory data: deps.dev and OSV.
OpenSSF Scorecard: 6.0 out of 10 (via deps.dev).
Sources: GitHub: locustio/locust, deps.dev: PyPI locust
Badge
Add this to a README to show the current verdict:
[](https://reporadar.ai/locustio/locust)Earlier verdicts
- Oct 14, 2026: Healthy
- Oct 14, 2026: Healthy
Computed 9 hours ago · method 2026.10.2