@hapi/hapi
HTTP Server framework
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@hapi/ammo | AI (dependencies): First-party @hapi ecosystem sub-package; stable dependency of hapi framework across versions. | ai | |
| dependencies | unvetted-dep:@hapi/call | AI (dependencies): First-party @hapi ecosystem sub-package; stable dependency of hapi framework across versions. | ai | |
| dependencies | unvetted-dep:@hapi/shot | AI (dependencies): First-party @hapi ecosystem sub-package; stable dependency of hapi framework across versions. | ai | |
| dependencies | unvetted-dep:@hapi/heavy | AI (dependencies): First-party @hapi ecosystem sub-package; stable dependency of hapi framework across versions. | ai | |
| dependencies | unvetted-dep:@hapi/mimos | AI (dependencies): First-party @hapi ecosystem sub-package; stable dependency of hapi framework across versions. | ai | |
| dependencies | unvetted-dep:@hapi/catbox | AI (dependencies): First-party @hapi ecosystem sub-package; stable dependency of hapi framework across versions. | ai | |
| dependencies | unvetted-dep:@hapi/podium | AI (dependencies): First-party @hapi ecosystem sub-package; stable dependency of hapi framework across versions. | ai | |
| dependencies | unvetted-dep:@hapi/somever | AI (dependencies): First-party @hapi ecosystem sub-package; stable dependency of hapi framework across versions. | ai | |
| dependencies | unvetted-dep:@hapi/subtext | AI (dependencies): First-party @hapi ecosystem sub-package; stable dependency of hapi framework across versions. | ai | |
| dependencies | unvetted-dep:@hapi/validate | AI (dependencies): First-party @hapi ecosystem sub-package; stable dependency of hapi framework across versions. | ai | |
| dependencies | unvetted-dep:@hapi/statehood | AI (dependencies): First-party @hapi ecosystem sub-package; stable dependency of hapi framework across versions. | ai | |
| dependencies | unvetted-dep:@hapi/catbox-memory | AI (dependencies): First-party @hapi ecosystem sub-package; stable dependency of hapi framework across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established package predating Sigstore provenance adoption; absence is expected and not a risk signal here. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 21.4.10 | 18 / 12 | |
| 21.4.9 | 18 / 12 | |
| 21.4.8 | 18 / 12 | |
| 21.4.7 | 18 / 12 | |
| 21.4.6 | 18 / 12 | |
| 21.4.5 | 18 / 12 | |
| 21.4.4 | 18 / 12 | |
| 21.4.3 | 18 / 12 | |
| 21.4.2 | 18 / 12 | |
| 21.4.1 | 18 / 12 | |
| 21.4.0 | 18 / 12 | |
| 21.3.12 | 18 / 12 | |
| 21.3.11 | 18 / 12 | |
| 21.3.10 | 18 / 12 | |
| 21.3.9 | 18 / 12 | |
| 21.3.8 | 18 / 12 | |
| 21.3.7 | 18 / 12 | |
| 21.3.6 | 18 / 12 | |
| 21.3.5 | 18 / 12 | |
| 21.3.4 | 18 / 12 | |
| 21.3.3 | 18 / 12 | |
| 21.3.2 | 18 / 12 | |
| 21.3.1 | 18 / 12 | |
| 21.3.0 | 18 / 12 | |
| 21.2.2 | 18 / 12 | |
| 21.2.1 | 18 / 12 | |
| 21.2.0 | 18 / 12 | |
| 21.1.0 | 18 / 12 | |
| 21.0.0 | 18 / 10 |
v21.4.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.3.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (marsup) than the most recent previously approved version (devinivy) on 2023-04-24, but marsup is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v21.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.3.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (devinivy) than the most recent previously approved version (marsup) on 2023-02-14, but devinivy is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v21.2.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (marsup) than the most recent previously approved version (devinivy) on 2023-02-11, but marsup is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v21.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.