@stdlib/assert-napi-equal-types
Assert that two Node-API data types are equal.
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 dependency pinned to a fork branch; no runtime impact. | ai | |
| npm-metadata | url-dep:tap-min | AI (npm-metadata): Dev-only test dependency; no runtime impact. | ai | |
| phantom-deps | phantom-dep:@stdlib/assert-napi-status-ok | AI (phantom-deps): Same-org stdlib dep used in native/C layer, not JS imports; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@stdlib/utils-library-manifest | AI (phantom-deps): Same-org stdlib build utility; not directly imported in JS but used in native build manifest; stable false positive. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.2.3 | 2 / 0 | |
| 0.2.2 | 2 / 0 | |
| 0.2.1 | 2 / 0 | |
| 0.2.0 | 2 / 5 | |
| 0.1.1 | 2 / 5 | |
| 0.1.0 | 2 / 5 | |
| 0.0.1 | 2 / 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.