jest-circus — Greenflagged

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
npm-metadata	suspicious-initial-version	AI (npm-metadata): jest-circus 0.0.0 is a known monorepo stub from the official Jest project; not a malicious placeholder.	ai	2026/05/22
bogus-package	bogus-package	AI (bogus-package): Stub/placeholder release from the official Jest monorepo; sparse metadata is expected for this version.	ai	2026/05/22
semgrep	semgrep:dynamic-require	AI (semgrep): Jest intentionally uses dynamic require() to load user-configured modules (e.g., prettierPath). This is a documented, expected pattern in Jest's test runner architecture, not a security risk.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): cpojer and mjesun are both known Jest/Meta maintainers; routine team rotation within the facebook/jest project.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Published in 2018, before Sigstore provenance existed. Expected for historical versions of jest-circus.	ai	2026/04/24
npm-metadata	no-description	AI (npm-metadata): Minor metadata omission common in monorepo-published packages; not a risk signal for jest-circus.	ai	2026/04/24
phantom-deps	phantom-dep:@jest/environment	AI (phantom-deps): Framework-scoped package loaded by convention in Jest test runner; stable for this package.	ai	2026/04/23
phantom-deps	phantom-dep:@types/node	AI (phantom-deps): Framework-scoped type definitions loaded by convention in Jest monorepo packages; stable pattern.	ai	2026/04/23
phantom-deps	phantom-dep:jest-runtime	AI (phantom-deps): Jest internal dependency referenced in config but not direct imports; expected in monorepo structure.	ai	2026/04/23
dependencies	unvetted-dep:co	AI (dependencies): co is a well-known async control-flow library and a long-standing Jest dependency; not a security risk.	ai	2026/04/21
dependencies	unvetted-dep:is-generator-fn	AI (dependencies): is-generator-fn is a tiny, well-known utility and a long-standing Jest dependency; not a security risk.	ai	2026/04/21
dependencies	unvetted-dep:pure-rand	AI (dependencies): pure-rand is a well-known PRNG library used by Jest for randomization; not a security risk.	ai	2026/04/21
dependencies	unvetted-dep:jest-each	AI (dependencies): jest-each is a first-party Jest monorepo package; unvetted status is a pipeline artifact.	ai	2026/04/21
dependencies	unvetted-dep:dedent	AI (dependencies): dedent is a widely-used string utility and a long-standing Jest dependency; not a security risk.	ai	2026/04/21

Versions (showing 51 of 136)

View all versions

Version	Deps	Published
30.4.2	20 / 8	2026-05-09
30.4.1	20 / 8	2026-05-08
30.4.0	20 / 8	2026-05-07
30.2.0	20 / 8	2025-09-28
30.1.3	20 / 8	2025-09-02
30.1.2	20 / 8	2025-09-01
30.1.1	20 / 8	2025-08-27
30.1.0	20 / 8	2025-08-27
30.0.5	20 / 8	2025-07-22
30.0.4	20 / 8	2025-07-02
30.0.3	20 / 8	2025-06-25
30.0.2	20 / 8	2025-06-19
30.0.1	20 / 8	2025-06-18
30.0.0	20 / 8	2025-06-10
29.7.0	20 / 8	2023-09-12
29.6.4	20 / 8	2023-08-24
29.6.3	20 / 8	2023-08-21
29.6.2	20 / 8	2023-07-27
29.6.1	20 / 9	2023-07-06
29.6.0	20 / 9	2023-07-04
29.5.0	20 / 8	2023-03-06
29.4.3	19 / 8	2023-02-15
29.4.2	19 / 8	2023-02-07
29.4.1	19 / 8	2023-01-26
29.4.0	19 / 8	2023-01-24
29.3.1	19 / 8	2022-11-08
29.3.0	19 / 8	2022-11-07
29.2.2	19 / 8	2022-10-24
29.2.1	19 / 8	2022-10-18
29.2.0	19 / 8	2022-10-14
29.1.2	19 / 8	2022-09-30
29.1.1	19 / 8	2022-09-28
29.1.0	19 / 8	2022-09-28
29.0.3	19 / 8	2022-09-10
29.0.2	19 / 8	2022-09-03
29.0.1	19 / 8	2022-08-26
29.0.0	19 / 8	2022-08-25
28.1.3	19 / 8	2022-07-13
28.1.2	19 / 8	2022-06-29
28.1.1	19 / 8	2022-06-07
28.1.0	19 / 8	2022-05-06
28.0.3	19 / 8	2022-04-29
28.0.2	19 / 8	2022-04-27
28.0.1	19 / 8	2022-04-26
28.0.0	19 / 8	2022-04-25
27.5.1	19 / 8	2022-02-08
27.5.0	19 / 9	2022-02-05
27.4.6	19 / 9	2022-01-04
27.4.5	19 / 10	2021-12-13
27.4.4	19 / 10	2021-12-10
27.4.2	19 / 10	2021-11-30

v30.4.2

1 finding

INFO No provenance attestation provenance

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

v30.4.1

1 finding

INFO No provenance attestation provenance

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

v30.4.0

2 findings

INFO No provenance attestation provenance

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

INFO Publisher changed: cpojer → simenb (on 2026-05-07) provenance

[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

1 finding

LOW No provenance attestation provenance

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

v30.1.3

1 finding

LOW No provenance attestation provenance

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

v30.1.2

1 finding

LOW No provenance attestation provenance

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

v30.1.1

1 finding

LOW No provenance attestation provenance

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

v30.1.0

1 finding

LOW No provenance attestation provenance

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

v30.0.5

1 finding

LOW No provenance attestation provenance

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

v30.0.4

1 finding

LOW No provenance attestation provenance

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

v30.0.3

1 finding

LOW No provenance attestation provenance

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

v30.0.2

1 finding

LOW No provenance attestation provenance

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

v30.0.1

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

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.

v29.7.0

1 finding

LOW No provenance attestation provenance

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

v29.6.4

1 finding

LOW No provenance attestation provenance

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

v29.6.3

1 finding

LOW No provenance attestation provenance

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

v29.6.2

1 finding

LOW No provenance attestation provenance

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

v29.6.1

1 finding

LOW No provenance attestation provenance

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

v29.6.0

1 finding

LOW No provenance attestation provenance

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

v29.5.0

1 finding

LOW No provenance attestation provenance

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

v29.4.3

1 finding

LOW No provenance attestation provenance

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

v29.4.2

1 finding

LOW No provenance attestation provenance

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

v29.4.1

1 finding

LOW No provenance attestation provenance

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

v29.4.0

1 finding

LOW No provenance attestation provenance

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

v29.3.1

1 finding

LOW No provenance attestation provenance

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

v29.3.0

1 finding

LOW No provenance attestation provenance

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

v29.2.2

1 finding

LOW No provenance attestation provenance

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

v29.2.1

1 finding

LOW No provenance attestation provenance

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

v29.2.0

1 finding

LOW No provenance attestation provenance

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

v29.1.2

1 finding

LOW No provenance attestation provenance

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

v29.1.1

1 finding

LOW No provenance attestation provenance

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

v29.1.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.

v29.0.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.

v29.0.2

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.

v29.0.1

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.

v29.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.

v28.1.3

1 finding

INFO No provenance attestation provenance

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

v28.1.2

1 finding

LOW No provenance attestation provenance

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

v28.1.1

1 finding

LOW No provenance attestation provenance

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

v28.1.0

1 finding

INFO No provenance attestation provenance

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

v28.0.3

1 finding

LOW No provenance attestation provenance

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

v28.0.2

1 finding

LOW No provenance attestation provenance

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

v28.0.1

1 finding

INFO No provenance attestation provenance

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

v28.0.0

1 finding

INFO No provenance attestation provenance

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

v27.5.1

1 finding

INFO No provenance attestation provenance

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

v27.5.0

1 finding

INFO No provenance attestation provenance

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

v27.4.6

1 finding

INFO No provenance attestation provenance

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

v27.4.5

1 finding

LOW No provenance attestation provenance

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

v27.4.4

1 finding

INFO No provenance attestation provenance

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

v27.4.2

1 finding

INFO No provenance attestation provenance

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