hapic
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): hapic is a well-established HTTP client package, not a typosquat of hapi; 51 versions and 1379 days of history confirm legitimacy. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.8.2 | 3 / 0 | |
| 2.8.1 | 3 / 0 | |
| 2.8.0 | 3 / 0 | |
| 2.7.0 | 3 / 0 | |
| 2.6.0 | 3 / 0 |
v2.8.2
2 findingsPackage name 'hapic' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.1
2 findingsPackage name 'hapic' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
2 findingsPackage name 'hapic' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
2 findingsPackage name 'hapic' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
2 findingsPackage name 'hapic' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.