@fastify/error
4.2.1 · 10 Oct 2026MIT23.5M / weekRepositoryHomepagenpmAtom feed
Your version
Security advisories
From OSV, open ones first. Each release line gets its own fix: an older major is fixed by a patch on that major, not by moving to the newest one.
No known security advisory for @fastify/error.
Quality and security signals
What npm and deps.dev say about the latest release. Signals, not a verdict.
- Licence
- ProvenancePresent, built from github.com/fastify/fastify-errorSays where the release was built and from which commit. It does not say the code is safe.
- Published byGitHub Actions4.2.1 was published by a different account than 4.2.0 (eomm). Often a new team member, sometimes a taken-over account.
- Maintainers on npm
- Size
- GitHub stars134 on fastify/fastify-error
- Last release4.2.1, 10 October 2026
- OpenSSF Scorecard7.1 / 10 · 24 Aug 2026Lowest: CII-Best-Practices 0, Fuzzing 0, Code-Review 3Grades the repository's practices (reviews, CI, branch protection), not the package's code.
Reading releases, release notes and advisories…
Registry facts last checked 20 Nov 2026. Releases and advisories last read 20 Nov 2026.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.