@fetch-mock/jestnpm
- latest 0.2.20
- last known licence MIT
- stars 1,307
- assessment attempted 8 days ago
- GitHub evidence observed 8 days ago
- registry checked 23 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 →Maintenance trends
Loading historical repository activity…
Signals · last 10 checks
Commits 90d
34
Open issues
4
Unanswered
0
Contributors
4
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node >=18.11.0. Source: the registry.
- Publishers on the registry — 1. Source: the registry.
- Open milestones — v3 1/1 done; v2 2/2 done; v4 2/2 done; v5 1/1 done; v6 3/3 done. Source: the repository's milestones.
- OpenSSF Scorecard — 5.1 / 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 8 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-11-01 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@fetch-mock/jest)Watch it
Get told when @fetch-mock/jest 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.