jest-each MIT 51 versions

jest-each

npm Repository

Parameterised tests for Jest

51

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-operationscpojermattphillips

Keywords

jestparameterisedtesteach

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): cpojer is a well-known Jest core maintainer; publisher change reflects legitimate Jest project governance transition to OpenJS Foundation.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): New maintainers (cpojer, rickhanlonii, aaronabramov, openjs-operations) are known Jest core contributors and OpenJS Foundation accounts — legitimate governance transition.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): Removed maintainers reflect Jest project governance reorganization under OpenJS Foundation; consistent with documented transition.	ai	2026/04/24
publish-pattern	new-deps-added	AI (publish-pattern): @jest/get-type is an internal Jest monorepo package replacing jest-get-type; a known v30 scope reorganization, not a suspicious external dependency.	ai	2026/04/24

Versions (showing 51 of 98)

View all versions

Version	Deps	Published
30.4.1	5 / 0	2026-05-08
30.4.0	5 / 0	2026-05-07
30.3.0	5 / 0	2026-03-10
30.2.0	5 / 0	2025-09-28
30.1.0	5 / 0	2025-08-27
30.0.5	5 / 0	2025-07-22
30.0.2	5 / 0	2025-06-19
30.0.1	5 / 0	2025-06-18
30.0.0	5 / 0	2025-06-10
29.7.0	5 / 0	2023-09-12
29.6.3	5 / 0	2023-08-21
29.6.2	5 / 0	2023-07-27
29.6.1	5 / 0	2023-07-06
29.6.0	5 / 0	2023-07-04
29.5.0	5 / 0	2023-03-06
29.4.3	5 / 0	2023-02-15
29.4.2	5 / 0	2023-02-07
29.4.1	5 / 0	2023-01-26
29.4.0	5 / 0	2023-01-24
29.3.1	5 / 0	2022-11-08
29.2.1	5 / 0	2022-10-18
29.2.0	5 / 0	2022-10-14
29.1.2	5 / 0	2022-09-30
29.1.0	5 / 0	2022-09-28
29.0.3	5 / 0	2022-09-10
29.0.2	5 / 0	2022-09-03
29.0.1	5 / 0	2022-08-26
29.0.0	5 / 0	2022-08-25
28.1.3	5 / 0	2022-07-13
28.1.1	5 / 0	2022-06-07
28.1.0	5 / 0	2022-05-06
28.0.2	5 / 0	2022-04-27
28.0.1	5 / 0	2022-04-26
28.0.0	5 / 0	2022-04-25
27.5.1	5 / 0	2022-02-08
27.5.0	5 / 0	2022-02-05
27.4.6	5 / 0	2022-01-04
27.4.2	5 / 0	2021-11-30
27.4.1	5 / 0	2021-11-30
27.4.0	5 / 0	2021-11-29
27.3.1	5 / 0	2021-10-19
27.3.0	5 / 0	2021-10-17
27.2.5	5 / 0	2021-10-08
27.2.4	5 / 0	2021-09-29
27.2.3	5 / 0	2021-09-28
27.2.2	5 / 0	2021-09-25
27.2.0	5 / 0	2021-09-13
27.1.1	5 / 0	2021-09-08
27.1.0	5 / 0	2021-08-27
27.0.6	5 / 0	2021-06-28
27.0.2	5 / 0	2021-05-29

v30.4.1

1 finding

LOW No provenance attestation provenance

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

v30.4.0

2 findings

LOW No provenance attestation provenance

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

2 findings

HIGH Publisher changed: simenb → cpojer (on 2025-06-19) provenance

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.

LOW No provenance attestation provenance

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

v30.0.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: simenb → cpojer (on 2025-06-18) provenance

[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

LOW No provenance attestation provenance

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

INFO Publisher changed: simenb → cpojer (on 2025-06-10) provenance

[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

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

1 finding

LOW No provenance attestation provenance

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

v29.0.3

1 finding

LOW No provenance attestation provenance

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

v29.0.2

1 finding

LOW No provenance attestation provenance

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

v29.0.1

1 finding

LOW No provenance attestation provenance

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

v29.0.0

1 finding

LOW No provenance attestation provenance

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