@umijs/es-module-parser
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
stormslowlyxiefengniansorrycczinkeyyutingzhao1991chenshuai2144fan576679268kuitoszombiejpeachscriptxiaohuoni
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): Standard napi-rs musl detection pattern; stable for this package. | ai | |
| semgrep | semgrep:child-process-execsync | AI (semgrep): execSync('which ldd') is the canonical napi-rs libc detection; benign. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped napi-rs native binding; missing metadata is typical for these packages. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.0.7 | 9 / 5 |
v0.0.7
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.