http-errors 1.2.2
Create HTTP error objects
http-errors@1.2.2 was published on 2014-09-22. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 0.6.
All http-errors versions · Permanent reference to 1.2.2 · Latest release
Package specifications
| Version | 1.2.2 |
|---|---|
| License declaration | MIT |
| Published | 2014-09-22T00:44:44.079Z |
| Node.js requirement | >= 0.6 |
| 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 | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 2 |
| Repository stars | 1561 |
| Repository forks | 116 |
Install http-errors 1.2.2
npm install http-errors@1.2.2 pnpm add http-errors@1.2.2 yarn add http-errors@1.2.2
Runtime dependencies
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.
- inherits@2.0.4 — direct
- statuses@1.0.4 — 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 | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
|---|---|
| Code-Review | 10/10 — all changesets reviewed |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Pinned-Dependencies | 6/10 — dependency not pinned by hash detected -- score normalized to 6 |
| 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 |
| Branch-Protection | 4/10 — branch protection is not maximal on development and all release branches |
| Security-Policy | 9/10 — security policy file detected |
| SAST | 8/10 — SAST tool detected but not run on all commits |
Evidence and freshness
- https://registry.npmjs.org/http-errors/1.2.2 — retrieved 2026-10-29T11:24:04.960Z
- https://api.deps.dev/v3/projects/github.com%2Fjshttp%2Fhttp-errors — retrieved 2026-10-29T06:01:33.854Z
- https://api.deps.dev/v3/systems/npm/packages/http-errors/versions/1.2.2 — retrieved 2026-10-29T11:24:06.721Z
- https://api.deps.dev/v3/systems/npm/packages/http-errors/versions/1.2.2:dependencies — retrieved 2026-10-29T11:24:06.736Z