jest-diff
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): jest-diff is part of the Facebook/Jest monorepo; size increases reflect TypeScript modularization in v25, not injected code. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from cpojer to mjesun is a documented legitimate Jest team transition; both are known Facebook/Jest contributors with strong track records. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): jest-diff 0.0.0 is a legitimate name-reservation stub by the Jest core team (cpojer). The 0.0.0 version is a known npm convention for namespace reservation by this publisher. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @jest/get-type and @jest/diff-sequences are first-party Jest monorepo packages at the same version; not third-party supply chain risk. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is consistent with Jest v25 refactor adding TypeScript declarations and modular source files; no malicious content. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers reflect the documented Jest transition to the OpenJS Foundation; openjs-operations and known Jest contributors are legitimate additions. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers (fb, gaearon, dmitriiabramov) reflect Meta's handoff of Jest to OpenJS Foundation — a known, documented governance change. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Missing description is standard for Jest workspace packages; not indicative of malice in this context. | ai | |
| bogus-package | bogus-package | AI (bogus-package): jest-diff is a workspace package in the Jest monorepo; missing description and inflated semver are expected for internal packages published as part of the Jest release cycle. | ai | |
| provenance | no-provenance | AI (provenance): Trusted publisher (cpojer, Jest core maintainer); lack of provenance is common and not a risk signal for this package. | ai | |
| dependencies | unvetted-dep:@jest/diff-sequences | AI (dependencies): @jest/diff-sequences is a sibling package in the same Jest monorepo, published simultaneously by the same trusted maintainer. | ai |
Versions (showing 51 of 124)
| Version | Deps | Published |
|---|---|---|
| 30.4.1 | 4 / 1 | |
| 30.4.0 | 4 / 1 | |
| 30.3.0 | 4 / 1 | |
| 30.2.0 | 4 / 1 | |
| 30.1.2 | 4 / 1 | |
| 30.1.1 | 4 / 1 | |
| 30.1.0 | 4 / 1 | |
| 30.0.5 | 4 / 1 | |
| 30.0.4 | 4 / 1 | |
| 30.0.3 | 4 / 1 | |
| 30.0.2 | 4 / 1 | |
| 30.0.1 | 4 / 1 | |
| 30.0.0 | 4 / 1 | |
| 29.7.0 | 4 / 2 | |
| 29.6.4 | 4 / 2 | |
| 29.6.3 | 4 / 2 | |
| 29.6.2 | 4 / 2 | |
| 29.6.1 | 4 / 2 | |
| 29.6.0 | 4 / 2 | |
| 29.5.0 | 4 / 2 | |
| 29.4.3 | 4 / 2 | |
| 29.4.2 | 4 / 2 | |
| 29.4.1 | 4 / 2 | |
| 29.4.0 | 4 / 2 | |
| 29.3.1 | 4 / 2 | |
| 29.2.1 | 4 / 2 | |
| 29.2.0 | 4 / 2 | |
| 29.1.2 | 4 / 2 | |
| 29.1.0 | 4 / 2 | |
| 29.0.3 | 4 / 2 | |
| 29.0.2 | 4 / 2 | |
| 29.0.1 | 4 / 2 | |
| 29.0.0 | 4 / 2 | |
| 28.1.3 | 4 / 2 | |
| 28.1.1 | 4 / 2 | |
| 28.1.0 | 4 / 2 | |
| 28.0.2 | 4 / 2 | |
| 28.0.1 | 4 / 2 | |
| 28.0.0 | 4 / 2 | |
| 27.5.1 | 4 / 2 | |
| 27.5.0 | 4 / 2 | |
| 27.4.6 | 4 / 2 | |
| 27.4.2 | 4 / 2 | |
| 27.4.1 | 4 / 2 | |
| 27.4.0 | 4 / 2 | |
| 27.3.1 | 4 / 2 | |
| 27.3.0 | 4 / 2 | |
| 27.2.5 | 4 / 2 | |
| 27.2.4 | 4 / 2 | |
| 27.2.3 | 4 / 2 | |
| 27.2.2 | 4 / 2 |
v30.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.4.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] 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.
v30.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.5.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-02-05. This could indicate a legitimate maintainer transition or an account compromise.
v27.4.6
2 findingsThis version was published by a different npm account than previous versions on 2022-01-04. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.2
2 findingsThis version was published by a different npm account than previous versions on 2021-11-30. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.1
2 findingsThis version was published by a different npm account than previous versions on 2021-11-30. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.0
2 findingsThis version was published by a different npm account than previous versions on 2021-11-29. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.3.1
2 findingsThis version was published by a different npm account than previous versions on 2021-10-19. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.3.0
2 findingsThis version was published by a different npm account than previous versions on 2021-10-17. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.5
2 findingsThis version was published by a different npm account than previous versions on 2021-10-08. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.4
2 findingsThis version was published by a different npm account than previous versions on 2021-09-29. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.3
2 findingsThis version was published by a different npm account than previous versions on 2021-09-28. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.2
2 findingsThis version was published by a different npm account than previous versions on 2021-09-25. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.