babel-preset-jest MIT 51 versions

babel-preset-jest

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-change	maintainer-added	AI (maintainer-change): New maintainers are known Jest core team members at Facebook/Meta. Roster changes are expected across a major version gap (v22→v27) for this high-profile project.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): Removed maintainers reflect normal team evolution within the Jest project at Facebook/Meta over the v22→v27 timespan.	ai	2026/04/24
publish-pattern	new-deps-added	AI (publish-pattern): babel-preset-current-node-syntax is a legitimate, well-known Babel preset replacing the removed syntax plugin; appropriate for Jest's modernization.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): cpojer → mjesun is a known legitimate transition within the Facebook/Jest maintainer team.	ai	2026/04/23
dependencies	unvetted-dep:babel-plugin-jest-unmock	AI (dependencies): babel-plugin-jest-unmock is a legitimate Jest ecosystem dependency consistent with this package's purpose as a Jest Babel preset.	ai	2026/04/23
npm-metadata	no-description	AI (npm-metadata): Early version of an official Facebook/Jest package; missing description is a cosmetic issue, not a malicious indicator given the package's age and download volume.	ai	2026/04/23

Versions (showing 51 of 78)

View all versions

Version	Deps	Published
29.6.3	2 / 0	2023-08-21
29.5.0	2 / 0	2023-03-06
29.4.3	2 / 0	2023-02-15
29.4.2	2 / 0	2023-02-07
29.4.0	2 / 0	2023-01-24
29.2.0	2 / 0	2022-10-14
29.0.2	2 / 0	2022-09-03
29.0.0	2 / 0	2022-08-25
28.1.3	2 / 0	2022-07-13
28.1.1	2 / 0	2022-06-07
28.0.2	2 / 0	2022-04-27
28.0.0	2 / 0	2022-04-25
27.5.1	2 / 0	2022-02-08
27.5.0	2 / 0	2022-02-05
27.4.0	2 / 0	2021-11-29
27.2.0	2 / 0	2021-09-13
27.0.6	2 / 0	2021-06-28
27.0.1	2 / 0	2021-05-25
26.6.2	2 / 0	2020-11-02
26.5.0	2 / 0	2020-10-05
26.3.0	2 / 0	2020-08-10
26.2.0	2 / 0	2020-07-30
26.1.0	2 / 0	2020-06-23
26.0.0	2 / 0	2020-05-04
25.5.0	2 / 0	2020-04-28
25.4.0	2 / 0	2020-04-19
25.3.0	2 / 0	2020-04-08
25.2.6	3 / 0	2020-04-02
25.2.1	3 / 0	2020-03-26
25.2.0	3 / 0	2020-03-25
25.1.0	3 / 0	2020-01-22
25.0.0	2 / 0	2019-08-22
24.9.0	2 / 0	2019-08-16
24.6.0	2 / 0	2019-04-01
24.3.0	2 / 0	2019-03-07
24.1.0	2 / 0	2019-02-05
24.0.0	2 / 0	2019-01-25
23.2.0	2 / 0	2018-06-25
23.0.1	2 / 0	2018-05-27
23.0.0	2 / 0	2018-05-24
22.4.4	2 / 0	2018-05-18
22.4.3	2 / 0	2018-03-21
22.4.1	2 / 0	2018-02-22
22.2.0	2 / 0	2018-02-07
22.1.0	2 / 0	2018-01-15
22.0.6	2 / 0	2018-01-11
22.0.3	2 / 0	2017-12-19
22.0.2	2 / 0	2017-12-19
22.0.1	2 / 0	2017-12-18
22.0.0	2 / 0	2017-12-18
21.2.0	2 / 0	2017-09-26

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

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

1 finding

LOW No provenance attestation provenance

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

v27.5.1

1 finding

LOW No provenance attestation provenance

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

v27.5.0

1 finding

LOW No provenance attestation provenance

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

v27.4.0

1 finding

LOW No provenance attestation provenance

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

v27.2.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: mjesun → simenb (on 2021-09-13) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2021-09-13. This could indicate a legitimate maintainer transition or an account compromise.

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

v26.6.2

1 finding

LOW No provenance attestation provenance

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

v26.5.0

1 finding

LOW No provenance attestation provenance

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

v26.3.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: scotthovestadt → simenb (on 2020-08-10) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-08-10. This could indicate a legitimate maintainer transition or an account compromise.

v26.2.0

1 finding

LOW No provenance attestation provenance

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

v26.1.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: scotthovestadt → simenb (on 2020-06-23) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-06-23. This could indicate a legitimate maintainer transition or an account compromise.

v26.0.0

1 finding

LOW No provenance attestation provenance

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

v25.5.0

1 finding

LOW No provenance attestation provenance

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

v25.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: scotthovestadt → simenb (on 2020-04-19) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-04-19. This could indicate a legitimate maintainer transition or an account compromise.

v25.3.0

1 finding

LOW No provenance attestation provenance

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

v25.2.6

1 finding

LOW No provenance attestation provenance

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

v25.2.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: rubennorte → simenb (on 2020-03-26) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-03-26. This could indicate a legitimate maintainer transition or an account compromise.

v25.2.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: scotthovestadt → simenb (on 2020-03-25) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-03-25. This could indicate a legitimate maintainer transition or an account compromise.

v25.1.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: rubennorte → davidzilburg (on 2020-01-22) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-01-22. This could indicate a legitimate maintainer transition or an account compromise.

v25.0.0

1 finding

LOW No provenance attestation provenance

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

v24.9.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: rubennorte → scotthovestadt (on 2019-08-16) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-08-16. This could indicate a legitimate maintainer transition or an account compromise.

v24.6.0

1 finding

LOW No provenance attestation provenance

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

v24.3.0

1 finding

LOW No provenance attestation provenance

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

v24.1.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: mjesun → rubennorte (on 2019-02-05) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-02-05. This could indicate a legitimate maintainer transition or an account compromise.

v24.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: mjesun → rubennorte (on 2019-01-25) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-01-25. This could indicate a legitimate maintainer transition or an account compromise.

v23.2.0

1 finding

LOW No provenance attestation provenance

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

v23.0.1

1 finding

LOW No provenance attestation provenance

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

v23.0.0

1 finding

LOW No provenance attestation provenance

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

v22.4.4

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.

v22.4.3

1 finding

LOW No provenance attestation provenance

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

v22.4.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: cpojer → mjesun (on 2018-02-22) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-02-22. This could indicate a legitimate maintainer transition or an account compromise.

v22.2.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 → mjesun (on 2018-02-07) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-02-07. This could indicate a legitimate maintainer transition or an account compromise.

v22.1.0

1 finding

LOW No provenance attestation provenance

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

v22.0.6

1 finding

LOW No provenance attestation provenance

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

v22.0.3

1 finding

LOW No provenance attestation provenance

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

v22.0.2

1 finding

LOW No provenance attestation provenance

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

v22.0.1

1 finding

LOW No provenance attestation provenance

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

v22.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: cpojer → mjesun (on 2017-12-18) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-12-18. This could indicate a legitimate maintainer transition or an account compromise.

v21.2.0

1 finding

LOW No provenance attestation provenance

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