← Home

@datagrok-libraries/statistics

npm
12
Versions
—
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

aparamonov_datagrokspodgrok

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:src/mpo/mpo-types.js AI (source-diff): Long line is an inline base64 sourceMappingURL comment, not obfuscated code; stable pattern for compiled TS in this package. ai
semgrep semgrep:new-function-constructor AI (semgrep): Used to deserialize user-defined fit function strings in a statistics library; not attacker-controlled remote input. ai
phantom-deps phantom-dep:dayjs AI (phantom-deps): Declared dependency; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:@types/seedrandom AI (phantom-deps): Type-only package loaded by convention; stable false positive for this package. ai

Versions (showing 12 of 12)

Version Deps Published
1.12.7 9 / 8
1.12.6 9 / 8
1.12.5 9 / 8
1.12.4 9 / 8
1.12.3 9 / 8
1.12.2 9 / 8
1.12.1 9 / 8
1.12.0 9 / 8
1.9.2 9 / 7
1.9.1 9 / 7
1.9.0 9 / 7
1.8.0 9 / 7

v1.12.7

2 findings
HIGH New obfuscated file: src/mpo/mpo-types.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

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

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

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

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

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

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

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

v1.9.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

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

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

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