npm-force-resolutions
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
rchaves
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval() is in Google Closure's base.js for JS environment detection — standard compiled ClojureScript artifact, not malicious. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is the core mechanism for running npm commands; expected for this tool's purpose. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): False positive: fires on SHA1 integrity string construction in compiled ClojureScript, not actual hex decoding of a payload. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Requires fixed known paths under out/goog/bootstrap/ — not truly dynamic/user-controlled. | ai | |
| phantom-deps | phantom-dep:json-format | AI (phantom-deps): Used in compiled ClojureScript output; phantom-dep heuristic misses indirect usage in compiled artifacts. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.0.10 | 3 / 0 |
v0.0.10
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.