@umijs/es-module-parser-win32-arm64-msvc
This is the **aarch64-pc-windows-msvc** binary for `@umijs/es-module-parser`
1
Versions
MIT
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 |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): Platform-specific native addon package; the .node binary is the sole deliverable by design. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse metadata is expected for platform-split native addon packages; not a spam indicator here. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.0.7 | 0 / 0 |
v0.0.7
2 findings
HIGH
Bundled binary files (1)
npm-metadata
Package contains compiled binaries that could be backdoors: • es-module-parser.win32-arm64-msvc.node
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.