← Home

@zuplo/test

npm Repository Homepage
4
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

zuplo-integrationsvazexqintotten

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 4 of 4)

Version Deps Published
1.4.0 0 / 13
1.3.0 0 / 13
1.2.0 0 / 13
1.0.2 0 / 13

v1.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

2 findings
MEDIUM Publisher changed: vazexqi → zuplo-integrations (on 2022-11-10, unremoved on npm for 1347d) provenance

This version was published by a different npm account (zuplo-integrations) than the most recent previously approved version (vazexqi) on 2022-11-10. It has since remained available on npm for 1347 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

1 finding
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.