autocannonnpm
- latest 9.0.0
- last known licence MIT
- stars 8,535
- assessment attempted today
- GitHub evidence observed today
- registry checked 18 days ago
- registry ↗
- repository ↗
Vulnerabilities, end of life and next steps
Check a specific version for known advisories, documented mitigations and evidence-backed earlier-version options. Maintenance health is separate from vulnerability status.
Review remediation options →Came back
After 2 years without a release, autocannon published 9.0.0 on 2026-11-06.
Usually this is a maintainer returning. It is also what a hijacked package looks like, so it is worth a glance at what changed before you upgrade.
Maintenance trends
Loading historical repository activity…
Signals · last 10 checks
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Publishers on the registry — 3. Source: the registry.
- OpenSSF Scorecard — 4.3 / 10 on 2026-08-24. Source: OpenSSF, via deps.dev. A third party's view of security practice, not part of the health score.
Third-party facts checked 6 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-11-07 | first verdict: coasting |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/autocannon)Watch it
Get told when autocannon changes state, changes licence, or is deprecated — instead of finding out during an incident.
Free for up to 25 packages. Signing in is a link sent to your email — there is no password to choose.