ref-napi
Turn Buffer instances into "pointers"
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package (3078 days old) from a highly trusted publisher; lack of Sigstore provenance is not a disqualifier for this package's history. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established native addon from a trusted, long-standing publisher (addaleax). Dormant-then-publish pattern is not suspicious given the maintainer's track record and the trivial nature of the release. | ai | |
| dependencies | unvetted-dep:node-gyp-build | AI (dependencies): node-gyp-build is a well-known, widely-used utility for native addon binary loading; not a risk for this package. | ai | |
| install-scripts | install-script:install | AI (install-scripts): node-gyp-build install script is the standard prebuild selection mechanism for native Node.js addons; stable and expected for ref-napi across all versions. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Prebuilt .node binaries are the expected output of prebuildify for this native addon; consistent with package.json prebuild scripts and the node-ffi-napi ecosystem pattern. | ai | |
| phantom-deps | phantom-dep:node-addon-api | AI (phantom-deps): node-addon-api is used in C++ binding compilation (binding.gyp), not imported in JS — this is the standard usage pattern for N-API addons. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 3.0.3 | 4 / 9 | |
| 3.0.2 | 4 / 9 | |
| 3.0.1 | 4 / 9 | |
| 3.0.0 | 4 / 9 | |
| 2.1.2 | 4 / 9 | |
| 2.1.1 | 4 / 9 | |
| 2.0.3 | 4 / 9 | |
| 2.0.0 | 4 / 9 |
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.