@es-shims/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 |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): This is a CLI tool that legitimately spawns child processes to run shim compliance tests. child_process usage is expected and benign for this package. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): @es-shims/api is a scoped package under the official es-shims org by ljharb; Levenshtein comparison to 'hapi' is a false positive that will never be relevant. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @es-shims/api is a scoped package under the official es-shims org; comparison to 'pg' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @es-shims/api is a scoped package under the official es-shims org; comparison to 'joi' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): @es-shims/api is a scoped package under the official es-shims org; comparison to 'ajv' is a false positive. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used to load a target package.json for ES shim API validation — expected CLI behavior, not arbitrary code execution. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 5 / 14 | |
| 3.0.3 | 5 / 14 | |
| 3.0.2 | 4 / 14 | |
| 3.0.1 | 4 / 14 | |
| 3.0.0 | 4 / 14 | |
| 2.5.1 | 5 / 8 |
v4.0.0
2 findingsPackage name '@es-shims/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.
v3.0.3
2 findingsPackage name '@es-shims/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.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.