jest-watcher
Delightful JavaScript Testing.
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): mjesun removal is part of the known Jest maintainer team restructuring; replaced by multiple active Facebook/Jest contributors. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2020 before Sigstore provenance was available on npm. Stable for historical versions of this package. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): Legitimate transition from mjesun to the broader Jest/Facebook maintainer team (simenb, fb, rubennorte, etc.). Well-documented OSS project governance change. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from mjesun to rubennorte reflects normal Jest team rotation at Facebook; both are known contributors. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are known Facebook/Meta engineers on the Jest team; legitimate team changes. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): jest-util is a sibling package in the facebook/jest monorepo; intra-monorepo dep addition is expected. | ai | |
| dependencies | unvetted-dep:string-length | AI (dependencies): string-length is a well-known benign utility used throughout the Jest ecosystem; no malicious signals and stable across versions. | ai | |
| dependencies | unvetted-dep:ansi-escapes | AI (dependencies): ansi-escapes is a well-known, widely used terminal utility library; its use in jest-watcher is expected and stable across versions. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is intentionally declared as a runtime dep in Jest packages for TypeScript type resolution; not a real phantom dependency concern. | ai |
Versions (showing 51 of 91)
| Version | Deps | Published |
|---|---|---|
| 30.4.1 | 8 / 0 | |
| 30.4.0 | 8 / 0 | |
| 30.3.0 | 8 / 0 | |
| 30.2.0 | 8 / 0 | |
| 30.1.3 | 8 / 0 | |
| 30.1.2 | 8 / 0 | |
| 30.1.1 | 8 / 0 | |
| 30.1.0 | 8 / 0 | |
| 30.0.5 | 8 / 0 | |
| 30.0.4 | 8 / 0 | |
| 30.0.2 | 8 / 0 | |
| 30.0.1 | 8 / 0 | |
| 30.0.0 | 8 / 0 | |
| 29.7.0 | 8 / 0 | |
| 29.6.4 | 8 / 0 | |
| 29.6.3 | 8 / 0 | |
| 29.6.2 | 8 / 0 | |
| 29.6.1 | 8 / 0 | |
| 29.6.0 | 8 / 0 | |
| 29.5.0 | 8 / 0 | |
| 29.4.3 | 8 / 0 | |
| 29.4.2 | 8 / 0 | |
| 29.4.1 | 8 / 0 | |
| 29.4.0 | 8 / 0 | |
| 29.3.1 | 8 / 0 | |
| 29.2.2 | 8 / 0 | |
| 29.2.1 | 8 / 0 | |
| 29.2.0 | 8 / 0 | |
| 29.1.2 | 8 / 0 | |
| 29.1.0 | 8 / 0 | |
| 29.0.3 | 8 / 0 | |
| 29.0.2 | 8 / 0 | |
| 29.0.1 | 8 / 0 | |
| 29.0.0 | 8 / 0 | |
| 28.1.3 | 8 / 0 | |
| 28.1.1 | 8 / 0 | |
| 28.1.0 | 8 / 0 | |
| 28.0.2 | 8 / 0 | |
| 28.0.1 | 8 / 0 | |
| 28.0.0 | 8 / 0 | |
| 27.5.1 | 7 / 0 | |
| 27.5.0 | 7 / 0 | |
| 27.4.6 | 7 / 0 | |
| 27.4.2 | 7 / 0 | |
| 27.4.1 | 7 / 0 | |
| 27.4.0 | 7 / 0 | |
| 27.3.1 | 7 / 0 | |
| 27.3.0 | 7 / 0 | |
| 27.2.5 | 7 / 0 | |
| 27.2.4 | 7 / 0 | |
| 27.2.3 | 7 / 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.3.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-03-10. 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.3
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
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 2025-08-27. This could indicate a legitimate maintainer transition or an account compromise.
v30.0.5
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 2025-07-22. This could indicate a legitimate maintainer transition or an account compromise.
v30.0.4
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 2025-07-02. This could indicate a legitimate maintainer transition or an account compromise.
v30.0.2
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 2025-06-19. This could indicate a legitimate maintainer transition or an account compromise.
v30.0.1
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 2025-06-18. This could indicate a legitimate maintainer transition or an account compromise.
v30.0.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 2025-06-10. This could indicate a legitimate maintainer transition or an account compromise.
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.2
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. Consider requesting the maintainer enable provenance via CI/CD.
v29.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.