@datagrok-libraries/compute-utils
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@datagrok/diff-grok | AI (dependencies): First-party datagrok namespace dep; consistent with this package's ecosystem and publisher. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all 172 versions of this package; publisher pattern does not use Sigstore attestation. | ai | |
| phantom-deps | phantom-dep:lodash.isequal | AI (phantom-deps): Referenced in config; stable false positive for this package. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used in formula/math expression evaluator (compileFormula); expected pattern for this library. | ai | |
| phantom-deps | phantom-dep:@types/lodash.clonedeepwith | AI (phantom-deps): Type-only package; not directly imported by convention. | ai | |
| phantom-deps | phantom-dep:lodash.clonedeepwith | AI (phantom-deps): Referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/uuid | AI (phantom-deps): Type-only package; not directly imported by convention. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 1.46.1 | 21 / 11 | |
| 1.46.0 | 21 / 11 | |
| 1.45.3 | 18 / 10 | |
| 1.45.2 | 18 / 10 | |
| 1.45.1 | 18 / 10 | |
| 1.45.0 | 18 / 10 | |
| 1.44.13 | 18 / 9 | |
| 1.44.12 | 18 / 9 | |
| 1.44.11 | 18 / 10 | |
| 1.44.10 | 18 / 10 | |
| 1.44.9 | 18 / 10 | |
| 1.44.8 | 18 / 10 | |
| 1.44.7 | 18 / 10 | |
| 1.44.5 | 18 / 10 | |
| 1.44.3 | 17 / 10 | |
| 1.44.2 | 17 / 10 | |
| 1.44.1 | 17 / 10 | |
| 1.43.11 | 17 / 11 | |
| 1.43.10 | 17 / 11 | |
| 1.43.9 | 17 / 11 | |
| 1.43.8 | 16 / 10 | |
| 1.43.7 | 16 / 10 | |
| 1.43.6 | 16 / 10 | |
| 1.43.5 | 16 / 10 | |
| 1.43.4 | 16 / 10 |
v1.46.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.