@data-client/test
Testing utilities for Data Client
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped testing utility that lists jest as a peer dep; not a typosquat of jest. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): Established @data-client scoped package; no relation to next.js. | ai | |
| typosquat | typosquat.levenshtein:vitest | AI (typosquat): Established @data-client scoped package; no relation to vitest. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.18.0 | 3 / 14 | |
| 0.16.0 | 3 / 14 | |
| 0.15.3 | 3 / 14 | |
| 0.15.0 | 3 / 14 |
v0.18.0
2 findingsPackage name '@data-client/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.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.