← Home

@stdlib/math-base-special-rempio2

Compute `x - nπ/2 = r`.

11
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

stdlibstdmathmathematicsmathremainderdivisionpipio2precision

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata url-dep:tape AI (npm-metadata): Dev-only test dependency pin, common across stdlib packages. ai
phantom-deps phantom-dep:@stdlib/types AI (phantom-deps): Same-org type-only dependency, stable false positive. ai
phantom-deps phantom-dep:@stdlib/napi-argv-double AI (phantom-deps): Native addon header dep; stable false positive for @stdlib native binding packages. ai
phantom-deps phantom-dep:@stdlib/napi-create-double AI (phantom-deps): Native addon header dep; stable false positive for @stdlib native binding packages. ai
phantom-deps phantom-dep:@stdlib/napi-argv AI (phantom-deps): Native addon header deps used in C source; not directly imported in JS. Stable pattern for @stdlib packages. ai
phantom-deps phantom-dep:@stdlib/utils-library-manifest AI (phantom-deps): Build manifest utility; used in build tooling, not directly imported in JS. Stable FP for @stdlib. ai
provenance no-provenance AI (provenance): stdlib-bot consistently publishes without Sigstore provenance; stable pattern across all @stdlib packages. ai
phantom-deps phantom-dep:@stdlib/napi-argv-float64array AI (phantom-deps): Native addon header dep; stable false positive for @stdlib native binding packages. ai
phantom-deps phantom-dep:@stdlib/napi-export AI (phantom-deps): Native addon header dep; stable false positive for @stdlib native binding packages. ai

Versions (showing 11 of 11)

Version Deps Published
0.3.1 16 / 0
0.3.0 16 / 0
0.2.1 10 / 0
0.2.0 11 / 18
0.1.0 11 / 17
0.0.6 8 / 17
0.0.5 7 / 17
0.0.4 7 / 17
0.0.3 7 / 17
0.0.2 7 / 17
0.0.1 7 / 17

v0.3.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] 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
INFO No provenance attestation provenance

[Accepted risk] 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
INFO No provenance attestation provenance

[Accepted risk] 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
INFO No provenance attestation provenance

[Accepted risk] 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
INFO No provenance attestation provenance

[Accepted risk] 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
INFO No provenance attestation provenance

[Accepted risk] 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
INFO No provenance attestation provenance

[Accepted risk] 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
INFO No provenance attestation provenance

[Accepted risk] 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
INFO No provenance attestation provenance

[Accepted risk] 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
INFO No provenance attestation provenance

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