@stdlib/napi-argv-int32
Convert a Node-API value to a signed 32-bit integer.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | url-dep:tape | AI (npm-metadata): Dev-only test dep pinned to a fork branch; stdlib monorepo convention, no runtime impact. | ai | |
| npm-metadata | url-dep:tap-min | AI (npm-metadata): Dev-only test reporter dep from git; benign, stable across stdlib packages. | ai | |
| phantom-deps | phantom-dep:@stdlib/napi-argv | AI (phantom-deps): Native N-API package; deps used via C headers/includes, not JS imports. Stable false positive for stdlib packages. | ai | |
| phantom-deps | phantom-dep:@stdlib/assert-napi-is-type | AI (phantom-deps): Same-org native dep used via C headers, not JS imports. Stable false positive. | ai | |
| phantom-deps | phantom-dep:@stdlib/assert-napi-status-ok | AI (phantom-deps): Same-org native dep used via C headers, not JS imports. Stable false positive. | ai | |
| phantom-deps | phantom-dep:@stdlib/utils-library-manifest | AI (phantom-deps): Build utility dep for native addon; not imported in JS. Stable false positive. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.2.3 | 4 / 0 | |
| 0.2.2 | 4 / 0 | |
| 0.2.1 | 4 / 0 | |
| 0.2.0 | 4 / 5 | |
| 0.1.1 | 4 / 5 | |
| 0.1.0 | 4 / 5 |
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.