@stdlib/assert-napi-is-type
Assert that a Node-API value is a specified Node-API data type.
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 pointing to maintainer's own fork; not shipped to consumers. | ai | |
| npm-metadata | url-dep:tap-min | AI (npm-metadata): Dev-only test dep from known contributor repo; not shipped to consumers. | ai | |
| phantom-deps | phantom-dep:@stdlib/assert-napi-status-ok | AI (phantom-deps): Same-org stdlib dep used in native addon context; phantom-dep heuristic fires on C-level usage not visible to JS import analysis. | ai | |
| phantom-deps | phantom-dep:@stdlib/utils-library-manifest | AI (phantom-deps): Same-org stdlib dep; library manifest used at build/native level, not JS import. | ai | |
| phantom-deps | phantom-dep:@stdlib/assert-napi-equal-types | AI (phantom-deps): Same-org stdlib dep; used in native addon layer, not directly imported in JS. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.2.3 | 3 / 0 | |
| 0.2.2 | 3 / 0 | |
| 0.2.1 | 3 / 0 | |
| 0.2.0 | 3 / 5 | |
| 0.1.1 | 3 / 5 | |
| 0.1.0 | 3 / 5 | |
| 0.0.1 | 3 / 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.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.