@stdlib/math-base-special-floor Apache-2.0 15 versions

@stdlib/math-base-special-floor

npm Repository Homepage

Round a double-precision floating-point number toward negative infinity.

15

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

stdlibstdmathmathematicsmathmath.floorfloorroundintegernearestvaluenumberdoubledouble-precisiondbl

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 for stdlib math bindings.	ai	2026/07/24
npm-metadata	url-dep:tape	AI (npm-metadata): Dev-only test dependency pin, not shipped to consumers.	ai	2026/07/24
phantom-deps	phantom-dep:@stdlib/math-base-napi-unary	AI (phantom-deps): Same-org NAPI binding dep; used at native layer, not directly imported in JS — stable false positive for stdlib packages.	ai	2026/04/29
phantom-deps	phantom-dep:@stdlib/utils-library-manifest	AI (phantom-deps): Same-org manifest utility; used at build/native layer, not directly imported in JS — stable false positive for stdlib packages.	ai	2026/04/29

Versions (showing 15 of 15)

Version	Deps	Published
0.2.4	2 / 0	2026-02-04
0.2.3	2 / 0	2024-07-27
0.2.2	2 / 0	2024-03-04
0.2.1	2 / 0	2024-02-23
0.2.0	2 / 12	2024-02-14
0.1.1	2 / 11	2023-10-09
0.1.0	2 / 11	2023-09-23
0.0.8	2 / 11	2022-02-16
0.0.7	2 / 11	2021-08-22
0.0.6	2 / 11	2021-07-07
0.0.5	2 / 11	2021-06-27
0.0.4	2 / 11	2021-06-16
0.0.3	2 / 11	2021-06-15
0.0.2	2 / 11	2021-06-14
0.0.1	2 / 11	2021-06-14

v0.2.3

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

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

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

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

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

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