confidence
Configuration API
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): devinivy is a well-established hapipal maintainer; this reflects a documented ecosystem transition from the original hapi.js author (hueniverse) to the hapipal community maintainers. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): hueniverse stepping back from hapipal packages is a well-known, documented transition in the hapi ecosystem; not indicative of a takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): joi replacing @hapi/joi is a known intentional rebranding migration in the hapi ecosystem; joi is a well-established, widely-used validation library. | ai | |
| phantom-deps | phantom-dep:alce | AI (phantom-deps): alce is a legitimate runtime dep used by the CLI binary; phantom detection fires because it's not directly imported in the main lib. | ai | |
| phantom-deps | phantom-dep:yargs | AI (phantom-deps): yargs is a legitimate runtime dep used by the CLI binary; phantom detection fires because it's not directly imported in the main lib. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 5.0.1 | 5 / 3 | |
| 5.0.0 | 4 / 3 | |
| 4.0.2 | 4 / 2 | |
| 4.0.1 | 4 / 2 | |
| 4.0.0 | 4 / 2 | |
| 3.0.2 | 4 / 2 | |
| 3.0.1 | 4 / 2 | |
| 3.0.0 | 4 / 2 | |
| 1.4.2 | 4 / 2 | |
| 1.4.1 | 4 / 2 | |
| 1.4.0 | 4 / 2 | |
| 1.3.0 | 4 / 2 | |
| 1.2.0 | 4 / 2 | |
| 1.1.0 | 4 / 2 | |
| 1.0.0 | 4 / 1 | |
| 0.12.1 | 4 / 1 | |
| 0.12.0 | 4 / 1 | |
| 0.11.1 | 4 / 1 | |
| 0.11.0 | 4 / 1 | |
| 0.10.0 | 4 / 1 | |
| 0.9.2 | 2 / 1 | |
| 0.9.1 | 2 / 1 | |
| 0.9.0 | 2 / 1 | |
| 0.8.1 | 2 / 1 | |
| 0.8.0 | 2 / 1 | |
| 0.7.2 | 2 / 1 | |
| 0.7.1 | 2 / 1 | |
| 0.7.0 | 2 / 1 | |
| 0.6.0 | 2 / 1 | |
| 0.5.0 | 2 / 1 | |
| 0.4.0 | 2 / 1 | |
| 0.3.0 | 2 / 1 | |
| 0.2.0 | 2 / 1 | |
| 0.1.0 | 0 / 2 |
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
2 findingsThis version was published by a different npm account than previous versions on 2020-09-21. 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.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.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 2018-11-20. This could indicate a legitimate maintainer transition or an account compromise.