← Home

jest-leak-detector

51
Versions
MIT
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

aaronabramovsimenbrickhanloniiopenjs-operationscpojer

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): jest-leak-detector is a legitimate sub-package of the Jest monorepo. SPAM flags on maintainers (cpojer, simenb, aaronabramov) are false positives for well-known Jest core team members. ai
npm-metadata no-description AI (npm-metadata): Monorepo sub-package with no description is a known pattern for jest packages; not indicative of malicious intent. ai
provenance no-provenance AI (provenance): Established Jest monorepo package; lack of Sigstore provenance is not a disqualifying signal for this well-known package. ai

Versions (showing 51 of 96)

View all versions
Version Deps Published
30.3.0 2 / 1
30.2.0 2 / 1
30.1.0 2 / 1
30.0.5 2 / 1
30.0.2 2 / 1
30.0.1 2 / 1
30.0.0 2 / 1
29.7.0 2 / 1
29.6.3 2 / 1
29.6.2 2 / 1
29.6.1 2 / 1
29.6.0 2 / 1
29.5.0 2 / 1
29.4.3 2 / 1
29.4.2 2 / 1
29.4.1 2 / 1
29.4.0 2 / 1
29.3.1 2 / 0
29.2.1 2 / 0
29.2.0 2 / 0
29.1.2 2 / 0
29.1.0 2 / 0
29.0.3 2 / 0
29.0.2 2 / 0
29.0.1 2 / 0
29.0.0 2 / 0
28.1.3 2 / 2
28.1.1 2 / 2
28.1.0 2 / 2
28.0.2 2 / 2
28.0.1 2 / 2
28.0.0 2 / 2
27.5.1 2 / 2
27.5.0 2 / 2
27.4.6 2 / 2
27.4.2 2 / 2
27.4.1 2 / 2
27.4.0 2 / 2
27.3.1 2 / 2
27.3.0 2 / 2
27.2.5 2 / 2
27.2.4 2 / 2
27.2.3 2 / 2
27.2.2 2 / 2
27.2.0 2 / 2
27.1.1 2 / 2
27.1.0 2 / 2
27.0.6 2 / 2
27.0.2 2 / 2
27.0.1 2 / 2
27.0.0 2 / 2

v30.3.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v30.1.0

1 finding
INFO No provenance attestation provenance

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

v30.0.2

1 finding
INFO No provenance attestation provenance

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