@enhavo/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 @enhavo org package; Levenshtein match on 'api' suffix is a false positive. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Same false-positive pattern; scoped package unrelated to pg. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Same false-positive pattern; scoped package unrelated to joi. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Same false-positive pattern; scoped package unrelated to ajv. | ai | |
| phantom-deps | phantom-dep:buffer | AI (phantom-deps): Browser polyfill declared for webpack config aliasing; not directly imported in source. | ai | |
| phantom-deps | phantom-dep:stream-browserify | AI (phantom-deps): Browser polyfill declared for webpack config aliasing; not directly imported in source. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.15.13 | 3 / 0 | |
| 0.15.12 | 3 / 0 | |
| 0.15.11 | 3 / 0 | |
| 0.15.10 | 3 / 0 | |
| 0.15.9 | 3 / 0 | |
| 0.15.8 | 3 / 0 | |
| 0.15.7 | 3 / 0 | |
| 0.15.6 | 3 / 0 | |
| 0.15.5 | 3 / 0 | |
| 0.15.4 | 3 / 0 | |
| 0.15.3 | 3 / 0 | |
| 0.15.2 | 3 / 0 | |
| 0.15.1 | 3 / 0 | |
| 0.14.7 | 3 / 0 | |
| 0.14.6 | 3 / 0 | |
| 0.14.5 | 3 / 0 |
v0.15.12
2 findingsPackage name '@enhavo/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.15.11
2 findingsPackage name '@enhavo/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.15.10
2 findingsPackage name '@enhavo/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.15.9
2 findingsPackage name '@enhavo/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.15.8
2 findingsPackage name '@enhavo/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.15.7
2 findingsPackage name '@enhavo/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.15.6
2 findingsPackage name '@enhavo/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.15.5
2 findingsPackage name '@enhavo/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.15.4
2 findingsPackage name '@enhavo/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.15.3
2 findingsPackage name '@enhavo/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.15.2
2 findingsPackage name '@enhavo/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.15.1
2 findingsPackage name '@enhavo/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.14.7
2 findingsPackage name '@enhavo/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.14.6
2 findingsPackage name '@enhavo/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.14.5
2 findingsPackage name '@enhavo/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.