autocorrect-node-win32-x64-msvc
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
huacnlee
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): Prebuilt NAPI .node binary is the sole purpose of this platform-specific sub-package; expected pattern for napi-rs builds. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Auto-generated platform shim packages intentionally lack README, repo URL, keywords, and deps — this is the standard napi-rs distribution pattern. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 2.14.0 | 0 / 0 |
v2.14.0
2 findings
HIGH
Bundled binary files (1)
npm-metadata
Package contains compiled binaries that could be backdoors: • autocorrect-node.win32-x64-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.