← Home

http-errors

Create HTTP error objects

30
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

ulisesgasconegestedougwilsonjongleberry

Keywords

httperror

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): dougwilson is a well-known jshttp/Express ecosystem maintainer, listed as contributor in package.json. Transition from jongleberry is a documented legitimate handoff within the jshttp org. ai
maintainer-change maintainer-added AI (maintainer-change): dougwilson is a prolific, trusted npm publisher (638 approved packages) and was already a contributor. Addition is a legitimate maintainer transition. ai
publish-pattern new-deps-added AI (publish-pattern): The added dependency 'inherits' is a foundational Node.js utility with no malicious history; its addition is benign for an HTTP error library. ai
provenance no-provenance AI (provenance): Package was published in 2015, predating Sigstore provenance. No provenance is expected for packages of this era. ai
dependencies unvetted-dep:depd AI (dependencies): depd is a well-established Express/jshttp ecosystem package for deprecation warnings; stable dependency for http-errors across versions. ai

Versions (showing 30 of 30)

Version Deps Published
2.0.1 5 / 9
2.0.0 5 / 9
1.8.1 5 / 9
1.8.0 5 / 9
1.7.3 5 / 9
1.7.2 5 / 9
1.7.1 5 / 9
1.7.0 5 / 9
1.6.3 4 / 9
1.6.2 4 / 9
1.6.1 4 / 7
1.6.0 4 / 7
1.5.1 3 / 7
1.5.0 3 / 6
1.4.0 2 / 2
1.3.1 2 / 2
1.3.0 2 / 2
1.2.8 2 / 2
1.2.7 2 / 2
1.2.6 2 / 2
1.2.5 2 / 2
1.2.4 2 / 2
1.2.3 2 / 2
1.2.2 2 / 2
1.2.1 2 / 2
1.2.0 1 / 2
1.1.0 1 / 2
1.0.1 1 / 2
1.0.0 1 / 2
0.0.1 0 / 0

v0.0.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.