← Home

@stdlib/number-float32-base-to-word

npm Repository Homepage

Return an unsigned 32-bit integer corresponding to the IEEE 754 binary representation of a single-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

stdlibstdtypesbaseutilitiesutilityutilsutiltypestypeconvertfloating-pointfloat32singlefloattobitsuint32wordunsigned32-bitintegerliteralnumberbinaryieee754

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:install AI (install-scripts): node-gyp rebuild is standard for stdlib native-binding packages. ai
npm-metadata url-dep:tape AI (npm-metadata): Long-standing stdlib devDependency pin, test-only, not runtime risk. ai
phantom-deps phantom-dep:@stdlib/utils-library-manifest AI (phantom-deps): Same-org stdlib manifest utility; declared as runtime dep but used indirectly — stable false positive for this package. ai

Versions (showing 12 of 12)

Version Deps Published
0.2.3 3 / 0
0.2.2 3 / 0
0.2.1 3 / 0
0.2.0 3 / 13
0.1.1 3 / 12
0.1.0 3 / 12
0.0.6 3 / 12
0.0.5 3 / 12
0.0.4 3 / 12
0.0.3 3 / 12
0.0.2 3 / 12
0.0.1 3 / 12

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.