fastify-error
`fastify-error@1.2.0` has been deprecated. Please use `@fastify/error@2.0.0` instead.
fastify-error@1.2.0 was published on 2022-04-27. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
Deprecated: Please use @fastify/error@2.0.0 instead
All fastify-error versions · Permanent reference to 1.2.0
Package specifications
| Version | 1.2.0 |
|---|---|
| License declaration | MIT |
| Published | 2022-04-27T13:19:32.977Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 787 B |
| Published file count | 3 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 2 |
| Repository stars | 135 |
| Repository forks | 24 |
Install fastify-error 1.2.0
npm install fastify-error@1.2.0 pnpm add fastify-error@1.2.0 yarn add fastify-error@1.2.0
Runtime dependencies
- process-warning ^1.0.0
- fastify-error-deprecated npm:fastify-error@1.1.0
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- fastify-error@1.1.0 — direct
- process-warning@1.0.0 — direct
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Maintained | 5/10 — 6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5 |
|---|---|
| Code-Review | 3/10 — Found 7/21 approved changesets -- score normalized to 3 |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Pinned-Dependencies | 10/10 — all dependencies are pinned |
| Token-Permissions | 10/10 — GitHub workflow tokens follow principle of least privilege |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Security-Policy | 10/10 — security policy file detected |
| SAST | 5/10 — SAST tool is not run on all commits -- score normalized to 5 |
Evidence and freshness
- https://registry.npmjs.org/fastify-error/1.2.0 — retrieved 2026-10-29T08:19:32.154Z
- https://api.deps.dev/v3/systems/npm/packages/fastify-error/versions/1.2.0 — retrieved 2026-10-29T08:19:32.718Z
- https://api.deps.dev/v3/systems/npm/packages/fastify-error/versions/1.2.0:dependencies — retrieved 2026-10-29T08:19:32.722Z
- https://api.deps.dev/v3/projects/github.com%2Ffastify%2Ffastify-error — retrieved 2026-10-29T08:19:32.861Z