← Home

@jest/pattern

npm Repository
6
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.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@types/node AI (phantom-deps): @types/node is a type-only dep used by convention; stable FP for this package. ai
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

Versions (showing 6 of 6)

Hide prereleases
Version Deps Published
30.4.0 2 / 0
30.0.1 2 / 0
30.0.0 2 / 0
30.0.0-beta.8 2 / 0
30.0.0-beta.6 2 / 0
30.0.0-beta.3 2 / 0

v30.4.0

2 findings
HIGH Publisher changed: cpojer → simenb (on 2026-05-07) provenance

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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v30.0.0-beta.8

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.

v30.0.0-beta.6

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.

v30.0.0-beta.3

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.