← Home

@hapi/boom

npm Repository Homepage

HTTP-friendly error objects

21
Versions
BSD-3-Clause
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

cjihrigmarsupnlfdevinivywyattlloydbensonnargonath

Keywords

errorhttp

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): devinivy is a known hapi ecosystem maintainer; publisher transition from nargonath is a legitimate team change within the hapijs org. ai
maintainer-change maintainer-removed AI (maintainer-change): cjihrig's removal is part of the known hapi maintainer reorganization; not indicative of takeover. ai
provenance no-provenance AI (provenance): Published in 2021 before Sigstore provenance was standard; informational only. ai

Versions (showing 21 of 21)

Version Deps Published
10.0.1 1 / 5
10.0.0 1 / 5
9.1.4 1 / 3
9.1.3 1 / 3
9.1.2 1 / 3
9.1.1 1 / 3
9.1.0 1 / 2
9.0.0 1 / 2
8.0.1 1 / 2
7.4.11 1 / 2
7.4.10 1 / 2
7.4.9 1 / 2
7.4.8 1 / 2
7.4.7 1 / 2
7.4.6 1 / 2
7.4.5 1 / 2
7.4.4 1 / 2
7.4.3 1 / 2
7.4.2 1 / 2
7.4.1 1 / 2
7.4.0 1 / 2

v10.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.1.3

2 findings
HIGH Publisher changed: nargonath → devinivy (on 2021-07-02) provenance

This version was published by a different npm account than previous versions on 2021-07-02. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.1.2

2 findings
HIGH Publisher changed: nargonath → devinivy (on 2021-03-16) provenance

This version was published by a different npm account than previous versions on 2021-03-16. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.1.1

2 findings
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: hueniverse → nargonath (on 2020-12-16) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-12-16. This could indicate a legitimate maintainer transition or an account compromise.

v9.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.