← Home

@stdlib/number-float64-base-set-high-word

Set the more significant 32 bits of a double-precision floating-point number.

12
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-pointfloatdoubledblwordswordhighsetsignsignbitsignificandmantissaexponentfractionieee754

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:install AI (install-scripts): gypfile native binding build, standard for stdlib numeric packages. ai
npm-metadata url-dep:tape AI (npm-metadata): Known stdlib devDependency pinned fork, not runtime risk. ai
phantom-deps phantom-dep:@stdlib/utils-library-manifest AI (phantom-deps): Same-org stdlib dependency; declared for native build manifest, not necessarily directly imported in JS. ai
phantom-deps phantom-dep:@stdlib/number-float64-base-to-words AI (phantom-deps): Same-org stdlib dependency; may be used indirectly via native/C layer rather than direct JS import. 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 / 21
0.1.1 5 / 20
0.1.0 5 / 20
0.0.6 5 / 20
0.0.5 5 / 20
0.0.4 5 / 20
0.0.3 5 / 20
0.0.2 5 / 20
0.0.1 5 / 20

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.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.