← Home

jest-leak-detector

npm Repository
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
provenance publisher-changed AI (provenance): simenb is a known Jest core maintainer; publisher rotation within the team is expected. ai
publish-pattern dormant-publish AI (publish-pattern): Jest publishes in batches with gaps; dormancy is normal for this monorepo package. ai
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 98)

View all versions
Version Deps Published
30.4.1 2 / 1
30.4.0 2 / 1
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

v30.4.1

2 findings
HIGH Publisher changed: cpojer → simenb (on 2026-05-08) provenance

This version was published by a different npm account than previous versions on 2026-05-08. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v30.4.0

2 findings
HIGH Publisher changed: cpojer → simenb (on 2026-05-07) provenance

This version was published by a different npm account than previous versions on 2026-05-07. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v30.2.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.1.0

1 finding
LOW No provenance attestation provenance

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

v30.0.5

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
LOW No provenance attestation provenance

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

v30.0.1

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.0

2 findings
HIGH Publisher changed: simenb → cpojer (on 2025-06-10) provenance

This version was published by a different npm account than previous versions on 2025-06-10. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v29.7.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.

v29.6.3

1 finding
INFO No provenance attestation provenance

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

v29.6.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.

v29.6.1

1 finding
INFO No provenance attestation provenance

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

v29.6.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.

v29.5.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.

v29.4.3

1 finding
INFO No provenance attestation provenance

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

v29.4.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.

v29.4.1

1 finding
INFO No provenance attestation provenance

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

v29.4.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.

v29.3.1

1 finding
INFO No provenance attestation provenance

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

v29.2.1

1 finding
INFO No provenance attestation provenance

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

v29.2.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.

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

v29.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.

v29.0.3

1 finding
INFO No provenance attestation provenance

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

v29.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.

v29.0.1

1 finding
INFO No provenance attestation provenance

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

v29.0.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.