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 24 of 124)
| Version | Deps | Published |
|---|---|---|
| 22.0.1 | 4 / 0 | |
| 22.0.0 | 4 / 0 | |
| 21.2.1 | 4 / 0 | |
| 21.2.0 | 4 / 0 | |
| 21.1.0 | 4 / 0 | |
| 21.0.2 | 4 / 0 | |
| 21.0.0 | 4 / 0 | |
| 20.0.3 | 4 / 0 | |
| 20.0.2 | 4 / 0 | |
| 20.0.1 | 4 / 0 | |
| 20.0.0 | 4 / 0 | |
| 19.0.0 | 4 / 0 | |
| 18.1.0 | 4 / 0 | |
| 18.0.0 | 4 / 0 | |
| 17.0.3 | 4 / 0 | |
| 17.0.2 | 4 / 0 | |
| 17.0.1 | 4 / 0 | |
| 17.0.0 | 4 / 0 | |
| 16.0.0 | 4 / 0 | |
| 15.1.0 | 4 / 0 | |
| 15.0.1 | 4 / 0 | |
| 15.0.0 | 4 / 0 | |
| 14.0.0 | 4 / 0 | |
| 0.0.0 | 0 / 0 |
v22.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.0
2 findingsThis version was published by a different npm account than previous versions on 2017-12-18. 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.
v21.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.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.
v18.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.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.
v15.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.
v14.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.
v0.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.