← Home

@stdlib/math-base-special-gamma-lanczos-sum-expg-scaled

npm Repository Homepage

Calculate a scaled Lanczos sum for the approximation of the gamma function.

13
Versions
Apache-2.0 AND BSL-1.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

stdlibstdmathmathematicsmathspecial functionspecialfunctiongammalanczosscaledapproxapproximationpolynomialrationalfactorialnumber

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 pinned to a git fork; not a runtime risk. ai
phantom-deps phantom-dep:@stdlib/math-base-napi-unary AI (phantom-deps): stdlib native binding dep; declared for native build tooling, not directly imported in JS — stable pattern for this org. ai
phantom-deps phantom-dep:@stdlib/utils-library-manifest AI (phantom-deps): stdlib manifest utility; declared for build tooling, not directly imported — stable pattern for this org. ai

Versions (showing 13 of 13)

Version Deps Published
0.3.0 2 / 0
0.2.2 2 / 0
0.2.1 0 / 0
0.2.0 0 / 17
0.1.1 0 / 16
0.1.0 0 / 16
0.0.7 0 / 15
0.0.6 0 / 15
0.0.5 0 / 15
0.0.4 0 / 15
0.0.3 0 / 15
0.0.2 0 / 15
0.0.1 0 / 15

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