@datagrok-libraries/test
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-api | AI (dependencies): datagrok-api is the core Datagrok platform library, expected dependency for all @datagrok-libraries packages. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): Scoped @datagrok-libraries package; no relation to next.js. | ai | |
| typosquat | typosquat.levenshtein:vitest | AI (typosquat): Scoped @datagrok-libraries package; no relation to vitest. | ai | |
| phantom-deps | phantom-dep:wu | AI (phantom-deps): Declared in dependencies; used via config/type references in this utility library. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped @datagrok-libraries package; not a typosquat of jest, it's a test utility for the Datagrok platform. | ai | |
| phantom-deps | phantom-dep:cash-dom | AI (phantom-deps): Declared in dependencies; used via config/type references in this utility library. | ai | |
| phantom-deps | phantom-dep:js-base64 | AI (phantom-deps): Declared in dependencies; used via config/type references in this utility library. | ai | |
| phantom-deps | phantom-dep:dayjs | AI (phantom-deps): Declared in dependencies; used via config/type references in this utility library. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.2.2 | 7 / 10 | |
| 1.2.1 | 7 / 10 | |
| 1.2.0 | 7 / 10 | |
| 1.1.0 | 7 / 10 | |
| 1.0.0 | 7 / 10 |
v1.2.2
2 findingsPackage name '@datagrok-libraries/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.