@datagrok-libraries/statistics
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:src/fit/const.js | AI (source-diff): Readable constants class; long lines are static assignments, not obfuscation. | ai | |
| source-diff | obfuscated-file:src/fit/new-fit-API.js | AI (source-diff): Minified/bundled compiled output, not true obfuscation; no malicious behavior present. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Internal datagrok team maintainer addition, consistent with org practice. | ai | |
| phantom-deps | phantom-dep:cash-dom | AI (phantom-deps): Used via config/convention in datagrok libraries, stable false positive. | ai | |
| 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 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 1.12.9 | 9 / 8 | |
| 1.12.8 | 9 / 8 | |
| 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.10.0 | 9 / 7 | |
| 1.9.2 | 9 / 7 | |
| 1.9.1 | 9 / 7 | |
| 1.9.0 | 9 / 7 | |
| 1.8.0 | 9 / 7 | |
| 1.7.0 | 7 / 6 | |
| 1.6.0 | 7 / 6 | |
| 1.5.0 | 7 / 6 | |
| 1.4.0 | 7 / 6 | |
| 1.3.6 | 5 / 6 | |
| 1.3.5 | 5 / 6 | |
| 1.3.4 | 5 / 6 | |
| 1.3.3 | 5 / 6 | |
| 1.3.2 | 5 / 6 | |
| 1.3.1 | 5 / 6 | |
| 1.3.0 | 5 / 6 |
v1.12.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (aparamonov_datagrok) than the most recent previously approved version (spodgrok) on 2025-10-22, but aparamonov_datagrok is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.7.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.