boom
HTTP-friendly error objects
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from arb to hueniverse (Eran Hammer) is the original hapi ecosystem creator reclaiming publishing rights. Legitimate and expected. | ai | |
| provenance | no-provenance | AI (provenance): Package published in 2018, before Sigstore provenance was available. Expected for this era of npm publishing. | ai |
Versions (showing 51 of 69)
| Version | Deps | Published |
|---|---|---|
| 7.3.0 | 1 / 3 | |
| 7.2.2 | 1 / 3 | |
| 7.2.1 | 1 / 3 | |
| 7.2.0 | 1 / 3 | |
| 7.1.1 | 1 / 3 | |
| 6.0.0 | 1 / 3 | |
| 5.3.3 | 1 / 2 | |
| 5.3.2 | 1 / 2 | |
| 5.2.0 | 1 / 3 | |
| 5.1.0 | 1 / 3 | |
| 5.0.0 | 1 / 3 | |
| 4.3.1 | 1 / 3 | |
| 4.3.0 | 1 / 3 | |
| 4.2.0 | 1 / 3 | |
| 4.1.0 | 1 / 3 | |
| 4.0.0 | 1 / 3 | |
| 3.2.2 | 1 / 3 | |
| 3.2.1 | 1 / 3 | |
| 3.2.0 | 1 / 3 | |
| 3.1.3 | 1 / 3 | |
| 3.1.2 | 1 / 3 | |
| 3.1.1 | 1 / 3 | |
| 3.1.0 | 1 / 3 | |
| 3.0.0 | 1 / 2 | |
| 2.10.1 | 1 / 2 | |
| 2.10.0 | 1 / 2 | |
| 2.9.0 | 1 / 2 | |
| 2.8.0 | 1 / 2 | |
| 2.7.2 | 1 / 2 | |
| 2.7.1 | 1 / 2 | |
| 2.7.0 | 1 / 2 | |
| 2.6.1 | 1 / 2 | |
| 2.6.0 | 1 / 1 | |
| 2.5.1 | 1 / 1 | |
| 2.5.0 | 1 / 1 | |
| 2.4.2 | 1 / 1 | |
| 2.4.1 | 1 / 1 | |
| 2.4.0 | 1 / 1 | |
| 2.3.0 | 1 / 1 | |
| 2.2.2 | 1 / 1 | |
| 2.2.1 | 1 / 1 | |
| 2.2.0 | 1 / 1 | |
| 2.1.0 | 1 / 1 | |
| 2.0.0 | 1 / 1 | |
| 1.2.1 | 1 / 1 | |
| 1.2.0 | 1 / 1 | |
| 1.1.2 | 1 / 1 | |
| 1.1.1 | 1 / 1 | |
| 1.1.0 | 1 / 1 | |
| 1.0.2 | 1 / 1 | |
| 1.0.1 | 1 / 1 |
v7.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.1
2 findingsThis version was published by a different npm account than previous versions on 2018-11-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-02-28. This could indicate a legitimate maintainer transition or an account compromise.
v7.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.