@2060.io/ffi-napi
1
Versions
—
License
Yes
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
genaris
Keywords
foreignfunctioninterfaceffilibffibindingcnapistable
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:install | AI (install-scripts): node-gyp-build is the canonical prebuilt-binary loader for N-API native addons; stable for this package. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): The flagged line is a constructor guard pattern (this instanceof check), not dynamic code execution. | ai | |
| phantom-deps | phantom-dep:node-addon-api | AI (phantom-deps): Used in native build config (binding.gyp), not directly imported in JS — stable false positive for native addons. | ai | |
| phantom-deps | phantom-dep:get-uv-event-loop-napi-h | AI (phantom-deps): Header-only dependency used in native build config, not imported in JS — stable false positive for native addons. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 4.0.9 | 6 / 8 |
v4.0.9
2 findings
HIGH
Package has 'install' script
install-scripts
Script: node-gyp-build
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.