@stdlib/math-base-special-log1pmx
Evaluate ln(1+x) - x.
Supply chain provenance
Status for the latest visible version.
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
Keywords
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 rebuild pattern used across stdlib packages. | ai | |
| npm-metadata | url-dep:tape | AI (npm-metadata): Dev-only fork dependency common across stdlib packages. | ai | |
| npm-metadata | url-dep:tap-min | AI (npm-metadata): Dev-only fork dependency common across stdlib packages. | ai | |
| phantom-deps | phantom-dep:@stdlib/math-base-napi-unary | AI (phantom-deps): Same-org stdlib dep; phantom detection is a false positive for this package's native binding pattern. | ai | |
| phantom-deps | phantom-dep:@stdlib/utils-library-manifest | AI (phantom-deps): Same-org stdlib utility; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@stdlib/math-base-special-log1p | AI (phantom-deps): Same-org stdlib dep; stable false positive for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.2.4 | 7 / 0 | |
| 0.2.3 | 7 / 0 | |
| 0.2.2 | 7 / 0 | |
| 0.1.1 | 7 / 9 | |
| 0.1.0 | 6 / 9 |
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
2 findingsScript: node-gyp rebuild
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
2 findingsScript: node-gyp rebuild
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.