@zuplo/test
1
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
zuplo-integrationsvazexqintotten
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 package @zuplo/test under the legitimate Zuplo org namespace; Levenshtein match to 'jest' is a false positive — no impersonation intent possible with a scoped name. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): Scoped package under @zuplo org; distance-2 match to 'next' is a false positive with no plausible impersonation vector. | ai | |
| typosquat | typosquat.levenshtein:vitest | AI (typosquat): Scoped package under @zuplo org; distance-2 match to 'vitest' is a false positive with no plausible impersonation vector. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Tiny payload is expected — package only exports TypeScript type definitions. Minimal README and no keywords are consistent with an internal utility package from an established org. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.4.0 | 0 / 13 |
v1.4.0
2 findings
HIGH
typosquat.levenshtein: Possible typosquat of 'jest'
typosquat
Package name '@zuplo/test' is 1 edit(s) away from popular package 'jest'.
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.