@hed-hog/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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped @hed-hog/api is a NestJS module; 'api' vs 'hapi' is a Levenshtein artifact on short names, not a real typosquat. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Same artifact; @hed-hog/api is unrelated to pg. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Same artifact; @hed-hog/api is unrelated to joi. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Same artifact; @hed-hog/api is unrelated to ajv. | ai | |
| phantom-deps | phantom-dep:@nestjs/mapped-types | AI (phantom-deps): @nestjs/mapped-types is a declared dependency used via NestJS config/decorator patterns; phantom-dep heuristic fires on indirect usage. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.0.8 | 4 / 0 | |
| 0.0.7 | 4 / 0 | |
| 0.0.5 | 4 / 0 | |
| 0.0.3 | 3 / 0 | |
| 0.0.1 | 3 / 0 |
v0.0.8
2 findingsPackage name '@hed-hog/api' 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.
v0.0.7
2 findingsPackage name '@hed-hog/api' 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.
v0.0.5
2 findingsPackage name '@hed-hog/api' 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.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.