@stdlib/math-base-special-copysign Apache-2.0 12 versions

@stdlib/math-base-special-copysign

npm Repository Homepage

Return a double-precision floating-point number with the magnitude of x and the sign of y.

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

stdlibstdmathmathmathematicsfloat64floatfloating-pointieee754doublecopysigncopysignbitsnumberdblspecialfunction

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	url-dep:tape	AI (npm-metadata): Dev-only test dependency URL pin, common in older stdlib packages, no runtime impact.	ai	2026/07/24
phantom-deps	phantom-dep:@stdlib/math-base-napi-binary	AI (phantom-deps): stdlib native binding helper; declared for optional native build, not directly imported in JS layer.	ai	2026/04/29
phantom-deps	phantom-dep:@stdlib/utils-library-manifest	AI (phantom-deps): stdlib build tooling dep; declared for manifest generation, not directly imported in JS layer.	ai	2026/04/29

Versions (showing 12 of 12)

Version	Deps	Published
0.2.3	7 / 0	2026-02-08
0.2.2	7 / 0	2024-07-28
0.2.1	7 / 0	2024-02-24
0.2.0	7 / 12	2024-02-14
0.1.0	7 / 11	2023-09-24
0.0.7	7 / 11	2022-11-15
0.0.6	5 / 11	2022-02-16
0.0.5	3 / 10	2021-08-22
0.0.4	3 / 10	2021-07-07
0.0.3	3 / 10	2021-06-27
0.0.2	3 / 10	2021-06-16
0.0.1	3 / 10	2021-06-15

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

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