← Home

@stdlib/number-float64-base-to-words

Split a double-precision floating-point number into a higher order word and a lower order word.

13
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

stdlib-botkgryteplaneshifterrreusser

Keywords

stdlibstdtypesbaseutilitiesutilityutilsutiltypestypefloat64floating-pointfloatdoubledblwordssplithighlowsignsignbitsignificandmantissaexponentfraction

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@stdlib/types AI (phantom-deps): Same-org stdlib package, type-only import pattern. ai
install-scripts install-script:install AI (install-scripts): node-gyp rebuild is standard for this native numeric binding package. ai
npm-metadata url-dep:tape AI (npm-metadata): Dev-only test dep pinned to a known fork, no runtime impact. ai
phantom-deps phantom-dep:@stdlib/os-byte-order AI (phantom-deps): Same-org stdlib dep; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:@stdlib/os-float-word-order AI (phantom-deps): Same-org stdlib dep; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:@stdlib/utils-library-manifest AI (phantom-deps): Same-org stdlib dep; phantom-dep heuristic false positive for this package. ai

Versions (showing 13 of 13)

Version Deps Published
0.2.3 7 / 0
0.2.2 7 / 0
0.2.1 7 / 0
0.2.0 8 / 18
0.1.1 8 / 17
0.1.0 8 / 17
0.0.7 8 / 17
0.0.6 7 / 16
0.0.5 7 / 16
0.0.4 7 / 16
0.0.3 7 / 16
0.0.2 7 / 16
0.0.1 7 / 16

v0.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.4

2 findings
HIGH Package has 'install' script install-scripts

Script: node-gyp rebuild

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.3

2 findings
HIGH Package has 'install' script install-scripts

Script: node-gyp rebuild

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.2

2 findings
HIGH Package has 'install' script install-scripts

Script: node-gyp rebuild

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1

2 findings
HIGH Package has 'install' script install-scripts

Script: node-gyp rebuild

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.