@hapi/hoek
General purpose node utilities
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): @hapi/hoek is a well-established hapi.js utility that migrated to the @hapi scope; inflated semver reflects pre-scoped package history, not a spam indicator. | ai | |
| provenance | publisher-changed | AI (provenance): marsup is a known long-time hapi.js core maintainer; the nargonath→marsup transition is a legitimate handoff within the hapi.js organization, not a suspicious takeover. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 11.0.7 | 0 / 5 | |
| 11.0.6 | 0 / 5 | |
| 11.0.5 | 0 / 5 | |
| 11.0.4 | 0 / 5 | |
| 11.0.3 | 0 / 5 | |
| 11.0.2 | 0 / 5 | |
| 11.0.1 | 0 / 5 | |
| 11.0.0 | 0 / 5 | |
| 10.0.1 | 0 / 5 | |
| 10.0.0 | 0 / 5 | |
| 9.3.0 | 0 / 4 | |
| 9.2.1 | 0 / 4 | |
| 9.2.0 | 0 / 3 | |
| 9.1.1 | 0 / 3 | |
| 9.1.0 | 0 / 2 | |
| 9.0.4 | 0 / 2 | |
| 9.0.3 | 0 / 2 | |
| 8.5.1 | 0 / 2 |
v11.0.6
2 findingsThis version was published by a different npm account than previous versions on 2024-10-24. 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.
v11.0.5
2 findingsThis version was published by a different npm account than previous versions on 2024-10-24. 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.
v11.0.4
2 findingsPackage 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 2023-12-05. This could indicate a legitimate maintainer transition or an account compromise.
v11.0.3
2 findingsPackage 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 2023-12-05. This could indicate a legitimate maintainer transition or an account compromise.
v11.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
2 findingsPackage 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 2022-12-13. This could indicate a legitimate maintainer transition or an account compromise.
v10.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
2 findingsPackage 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 2021-04-17. This could indicate a legitimate maintainer transition or an account compromise.
v9.1.1
2 findingsPackage 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 2020-12-27. This could indicate a legitimate maintainer transition or an account compromise.
v9.1.0
2 findingsPackage 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 2020-09-02. This could indicate a legitimate maintainer transition or an account compromise.
v9.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.