@stdlib/math-base-assert-is-finite
Test if a double-precision floating-point numeric value is finite.
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 |
|---|---|---|---|---|
| install-scripts | install-script:install | AI (install-scripts): Standard node-gyp native build step, consistent across stdlib math packages. | ai | |
| npm-metadata | url-dep:tape | AI (npm-metadata): Dev-only test dependency pinned to a fork; no runtime impact. | ai | |
| phantom-deps | phantom-dep:@stdlib/napi-argv-double | AI (phantom-deps): N-API deps declared for native binding support, not imported in JS — stable stdlib pattern. | ai | |
| phantom-deps | phantom-dep:@stdlib/napi-argv | AI (phantom-deps): N-API deps declared for native binding support, not imported in JS — stable stdlib pattern. | ai | |
| phantom-deps | phantom-dep:@stdlib/utils-library-manifest | AI (phantom-deps): Library manifest utility used at build/native level, not imported in JS — stable stdlib pattern. | ai | |
| phantom-deps | phantom-dep:@stdlib/napi-create-int32 | AI (phantom-deps): N-API deps declared for native binding support, not imported in JS — stable stdlib pattern. | ai | |
| phantom-deps | phantom-dep:@stdlib/napi-export | AI (phantom-deps): N-API deps declared for native binding support, not imported in JS — stable stdlib pattern. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.2.3 | 7 / 0 | |
| 0.2.2 | 3 / 0 | |
| 0.2.1 | 3 / 0 | |
| 0.2.0 | 3 / 11 | |
| 0.1.1 | 3 / 10 | |
| 0.1.0 | 3 / 10 | |
| 0.0.7 | 3 / 9 | |
| 0.0.6 | 3 / 9 | |
| 0.0.5 | 3 / 9 | |
| 0.0.4 | 3 / 9 | |
| 0.0.3 | 3 / 9 | |
| 0.0.2 | 3 / 9 | |
| 0.0.1 | 3 / 9 |
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.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
2 findingsScript: node-gyp rebuild
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
2 findingsScript: node-gyp rebuild
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
2 findingsScript: node-gyp rebuild
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
2 findingsScript: node-gyp rebuild
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
2 findingsScript: node-gyp rebuild
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.