@jest/pattern
2
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
aaronabramovsimenbrickhanloniiopenjs-operationscpojer
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Jest monorepo packages routinely start at high semver versions aligned with the monorepo release, have minimal READMEs, and no keywords. These signals are structural false positives for this package family. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal Jest monorepo utility packages commonly omit standalone descriptions; not indicative of malicious intent. | ai | |
| dependencies | unvetted-dep:jest-regex-util | AI (dependencies): jest-regex-util is a sibling Jest monorepo package published at the same version; unvetted status is a pipeline lag, not a real risk. | ai |
v30.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.