@jest/test-sequencer MIT 51 versions

@jest/test-sequencer

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
—	maintainer-added	—	sean	2026/05/21
—	publisher-changed	—	sean	2026/05/21
npm-metadata	no-description	AI (npm-metadata): Jest core package; missing description is a metadata oversight, not a malware signal.	ai	2026/05/21

Versions (showing 51 of 103)

View all versions

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

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

1 finding

LOW No provenance attestation provenance

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

v30.3.0

2 findings

HIGH Publisher changed: simenb → cpojer (on 2026-03-10) provenance

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

v30.2.0

2 findings

HIGH Publisher changed: simenb → cpojer (on 2025-09-28) provenance

This version was published by a different npm account than previous versions on 2025-09-28. 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.1.3

2 findings

HIGH Publisher changed: simenb → cpojer (on 2025-09-02) provenance

This version was published by a different npm account than previous versions on 2025-09-02. 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.1.2

2 findings

HIGH Publisher changed: simenb → cpojer (on 2025-09-01) provenance

This version was published by a different npm account than previous versions on 2025-09-01. 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.1.1

2 findings

HIGH Publisher changed: simenb → cpojer (on 2025-08-27) provenance

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

2 findings

HIGH Publisher changed: simenb → cpojer (on 2025-08-27) provenance

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

2 findings

HIGH Publisher changed: simenb → cpojer (on 2025-07-22) provenance

This version was published by a different npm account than previous versions on 2025-07-22. 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.4

2 findings

HIGH Publisher changed: simenb → cpojer (on 2025-07-02) provenance

This version was published by a different npm account than previous versions on 2025-07-02. 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.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

1 finding

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