jest-mock
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 | source-size-tripled | AI (source-diff): Size increase is explained by the addition of the new browser-targeted ES5 bundle with polyfills, an intentional build artifact for jest-mock. | ai | |
| source-diff | net-exec-file:build-es5/index.js | AI (source-diff): build-es5/index.js is an intentional UMD/ES5 browser bundle (referenced in package.json 'browser' field). The 'network+exec' signals are UMD boilerplate (typeof window, define(factory)) — not actual network I/O or malicious code execution. | ai | |
| dependencies | unvetted-dep:@jest/types | AI (dependencies): @jest/types is a first-party sibling package in the jestjs/jest monorepo, always released in lockstep with jest-mock. Not a third-party unknown dependency. | ai | |
| dependencies | unvetted-dep:jest-util | AI (dependencies): jest-util is a first-party sibling package in the jestjs/jest monorepo, always released in lockstep with jest-mock. Not a third-party unknown dependency. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @jest/types and @types/node are legitimate Jest ecosystem packages introduced in the v26 monorepo refactor; not suspicious. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Size drop from v22 to v26 reflects intentional refactoring (type extraction to @jest/types, TypeScript adoption); not a stub replacement. | ai | |
| provenance | publisher-changed | AI (provenance): simenb is a known Jest core contributor at Meta/Facebook; the publisher change from cpojer reflects a legitimate team transition, not a compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are known Jest team members at Meta/Facebook; consistent with legitimate team evolution across major versions. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers reflect normal team turnover at Meta/Facebook; no signs of hostile takeover. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): jest-mock 0.0.0 is a well-known namespace reservation stub by the Jest core team (cpojer). The 0.0.0 version is intentional and not indicative of malicious activity. | ai | |
| provenance | no-provenance | AI (provenance): jest-mock is a long-established Facebook/Jest package; absence of Sigstore provenance is expected for packages of this age and is not a risk signal here. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): jest-mock intentionally uses new Function() to create named mock constructors — a documented, stable internal pattern with no external input. Not a security risk for this package. | ai | |
| phantom-deps | phantom-dep:@jest/types | AI (phantom-deps): Type-only dependency; not directly imported at runtime is expected for TypeScript type packages in Jest's ecosystem. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Jest monorepo packages routinely omit descriptions in published package.json; not a malware signal for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): jest-mock is a core Jest monorepo package; inflated semver, missing description, and no keywords are expected artifacts of monorepo publishing, not spam indicators. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is a type-only dependency; not being directly imported at runtime is standard and expected. | ai |
Versions (showing 51 of 125)
| Version | Deps | Published |
|---|---|---|
| 30.4.1 | 3 / 0 | |
| 30.4.0 | 3 / 0 | |
| 30.2.0 | 3 / 0 | |
| 30.0.5 | 3 / 0 | |
| 30.0.2 | 3 / 0 | |
| 30.0.1 | 3 / 0 | |
| 30.0.0 | 3 / 0 | |
| 29.7.0 | 3 / 2 | |
| 29.6.3 | 3 / 2 | |
| 29.6.2 | 3 / 2 | |
| 29.6.1 | 3 / 2 | |
| 29.6.0 | 3 / 2 | |
| 29.5.0 | 3 / 2 | |
| 29.4.3 | 3 / 2 | |
| 29.4.2 | 3 / 2 | |
| 29.4.1 | 3 / 2 | |
| 29.4.0 | 3 / 2 | |
| 29.3.1 | 3 / 2 | |
| 29.3.0 | 3 / 2 | |
| 29.2.2 | 3 / 2 | |
| 29.2.1 | 3 / 2 | |
| 29.2.0 | 3 / 2 | |
| 29.1.2 | 3 / 2 | |
| 29.1.1 | 3 / 2 | |
| 29.1.0 | 3 / 2 | |
| 29.0.3 | 2 / 2 | |
| 29.0.2 | 2 / 2 | |
| 29.0.1 | 2 / 2 | |
| 29.0.0 | 2 / 2 | |
| 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 / 0 | |
| 27.5.0 | 2 / 0 | |
| 27.4.6 | 2 / 0 | |
| 27.4.2 | 2 / 0 | |
| 27.4.1 | 2 / 0 | |
| 27.4.0 | 2 / 0 | |
| 27.3.0 | 2 / 0 | |
| 27.2.5 | 2 / 0 | |
| 27.2.4 | 2 / 0 | |
| 27.2.3 | 2 / 0 | |
| 27.1.1 | 2 / 0 | |
| 27.1.0 | 2 / 0 | |
| 27.0.6 | 2 / 0 | |
| 27.0.3 | 2 / 0 | |
| 27.0.2 | 2 / 0 | |
| 27.0.1 | 2 / 0 |
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
2 findingsThis version was published by a different npm account than previous versions on 2025-09-28. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.5
2 findingsThis version was published by a different npm account than previous versions on 2025-07-22. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.2
2 findingsThis version was published by a different npm account than previous versions on 2025-06-19. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.1
2 findingsThis version was published by a different npm account than previous versions on 2025-06-18. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.1.3
2 findingsThis version was published by a different npm account than previous versions on 2022-07-13. 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.
v28.1.1
2 findingsThis version was published by a different npm account than previous versions on 2022-06-07. 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.
v28.1.0
2 findingsThis version was published by a different npm account than previous versions on 2022-05-06. 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.
v28.0.2
2 findingsThis version was published by a different npm account than previous versions on 2022-04-27. 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.
v28.0.1
2 findingsThis version was published by a different npm account than previous versions on 2022-04-26. 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.
v28.0.0
2 findingsThis version was published by a different npm account than previous versions on 2022-04-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.
v27.5.1
2 findingsThis version was published by a different npm account than previous versions on 2022-02-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.5.0
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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.1.1
2 findingsThis version was published by a different npm account than previous versions on 2021-09-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.1.0
2 findingsThis version was published by a different npm account than previous versions on 2021-08-27. 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.0.6
2 findingsThis version was published by a different npm account than previous versions on 2021-06-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.0.3
2 findingsThis version was published by a different npm account than previous versions on 2021-05-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.0.2
2 findingsThis version was published by a different npm account than previous versions on 2021-05-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.0.1
2 findingsThis version was published by a different npm account than previous versions on 2021-05-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.