jest-regex-util
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): cpojer→simenb is a known Jest maintainer transition; simenb is a core Jest contributor. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Jest publishes in batches with gaps; dormancy is normal for this monorepo package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package; missing description is stable and benign. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 30.4.0 | 0 / 1 | |
| 30.0.1 | 0 / 1 | |
| 30.0.0 | 0 / 1 | |
| 29.6.3 | 0 / 1 | |
| 29.4.3 | 0 / 1 | |
| 29.4.2 | 0 / 1 | |
| 29.2.0 | 0 / 1 | |
| 29.0.0 | 0 / 1 | |
| 28.0.2 | 0 / 1 | |
| 28.0.0 | 0 / 1 | |
| 27.5.1 | 0 / 1 | |
| 27.5.0 | 0 / 1 | |
| 27.4.0 | 0 / 1 | |
| 27.0.6 | 0 / 1 | |
| 27.0.1 | 0 / 1 | |
| 26.0.0 | 0 / 1 | |
| 25.2.6 | 0 / 1 | |
| 25.2.1 | 0 / 1 | |
| 25.2.0 | 0 / 1 | |
| 25.1.0 | 0 / 0 | |
| 25.0.0 | 0 / 0 | |
| 24.9.0 | 0 / 0 | |
| 24.3.0 | 0 / 0 | |
| 24.2.0 | 0 / 0 | |
| 24.0.0 | 0 / 0 | |
| 23.3.0 | 0 / 0 | |
| 23.0.0 | 0 / 0 | |
| 22.4.3 | 0 / 0 | |
| 22.1.0 | 0 / 0 | |
| 22.0.6 | 0 / 0 | |
| 22.0.5 | 0 / 0 | |
| 22.0.3 | 0 / 0 | |
| 21.2.0 | 0 / 0 | |
| 21.1.0 | 0 / 0 | |
| 21.0.2 | 0 / 0 | |
| 21.0.0 | 0 / 0 | |
| 20.0.3 | 0 / 0 | |
| 20.0.2 | 0 / 0 | |
| 20.0.1 | 0 / 0 | |
| 20.0.0 | 0 / 0 | |
| 19.0.0 | 0 / 0 | |
| 0.0.0 | 0 / 0 |
v30.4.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.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.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.2.0
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. Consider requesting the maintainer enable provenance via CI/CD.