@stdlib/number-float64-base-from-words
Create a double-precision floating-point number from a higher order word and a lower order word.
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): node-gyp rebuild is standard native binding build step for stdlib packages. | ai | |
| npm-metadata | url-dep:tape | AI (npm-metadata): Longstanding devDependency pin across stdlib packages, not runtime risk. | ai | |
| phantom-deps | phantom-dep:@stdlib/utils-library-manifest | AI (phantom-deps): Same-org stdlib dep; phantom-dep heuristic fires on indirect/native usage patterns common in stdlib packages. | ai | |
| phantom-deps | phantom-dep:@stdlib/number-float64-base-to-words | AI (phantom-deps): Same-org stdlib dep; phantom-dep heuristic fires on indirect/native usage patterns common in stdlib packages. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.2.3 | 5 / 0 | |
| 0.2.2 | 5 / 0 | |
| 0.2.1 | 5 / 0 | |
| 0.2.0 | 5 / 14 | |
| 0.1.1 | 5 / 13 | |
| 0.1.0 | 5 / 13 | |
| 0.0.6 | 5 / 13 | |
| 0.0.5 | 5 / 13 | |
| 0.0.4 | 5 / 13 | |
| 0.0.3 | 5 / 13 | |
| 0.0.2 | 5 / 13 | |
| 0.0.1 | 5 / 13 |
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.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
1 findingPackage 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.