jest-validate MIT 51 versions

jest-validate

npm Repository

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

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 known Jest core maintainer; publisher rotation is expected for Jest 30.	ai	2026/05/30
maintainer-change	maintainer-added	AI (maintainer-change): OpenJS Foundation transition; all added maintainers are known Jest contributors.	ai	2026/05/30
maintainer-change	maintainer-removed	AI (maintainer-change): Old Meta/FB-era maintainers removed as part of OpenJS transition.	ai	2026/05/30
bogus-package	bogus-package	AI (bogus-package): False positive; spam-publisher signal is wrong — these are established Jest maintainers.	ai	2026/05/30
npm-metadata	no-description	AI (npm-metadata): Jest monorepo sub-package; missing description is a stable metadata quirk, not a malware signal.	ai	2026/05/18

Versions (showing 51 of 121)

View all versions

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

v30.4.1

2 findings

HIGH Publisher changed: cpojer → simenb (on 2026-05-08) provenance

This version was published by a different npm account than previous versions on 2026-05-08. 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.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.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

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

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.

LOW No provenance attestation provenance

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

v30.0.0

2 findings

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

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.

LOW No provenance attestation provenance

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

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