← Home

@stdlib/math-base-special-ln

Evaluate the natural logarithm of a double-precision floating-point number.

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

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:install AI (install-scripts): Standard node-gyp rebuild for native math binding, consistent across stdlib packages. ai
npm-metadata url-dep:tap-min AI (npm-metadata): Dev-only test reporter dependency; no runtime impact. ai
npm-metadata url-dep:tape AI (npm-metadata): Common dev-only tape fork dependency, not a runtime risk. ai
phantom-deps phantom-dep:@stdlib/math-base-napi-unary AI (phantom-deps): Same-org stdlib dep used for native binding; not directly imported in JS but referenced via native build manifest. ai
phantom-deps phantom-dep:@stdlib/utils-library-manifest AI (phantom-deps): Same-org stdlib utility for native library manifests; indirect usage pattern is stable across stdlib packages. ai

Versions (showing 13 of 13)

Version Deps Published
0.2.5 7 / 0
0.2.4 7 / 0
0.2.3 7 / 0
0.2.2 7 / 0
0.2.1 7 / 0
0.2.0 7 / 19
0.1.0 7 / 18
0.0.6 5 / 11
0.0.5 5 / 11
0.0.4 5 / 11
0.0.3 5 / 11
0.0.2 5 / 11
0.0.1 5 / 11

v0.2.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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

v0.2.0

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

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