jest-resolve-dependencies MIT 49 versions

jest-resolve-dependencies

npm Repository

49

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): gaearon (Dan Abramov) is a well-known Meta/React ecosystem contributor; addition to the Jest maintainer list is consistent with legitimate project governance.	ai	2026/04/23
provenance	publisher-changed	AI (provenance): The cpojer→mjesun transition is a documented, legitimate Jest team maintainer change from Jan 2018; stable for this package across all versions.	ai	2026/04/23
npm-metadata	suspicious-initial-version	AI (npm-metadata): jest-resolve-dependencies 0.0.0 is a known Jest monorepo placeholder pattern published by a trusted core maintainer; 0.0.0 is not suspicious in this context.	ai	2026/04/23
npm-metadata	no-description	AI (npm-metadata): Internal monorepo package; missing description is expected and not a malware signal.	ai	2026/04/21
phantom-deps	phantom-dep:jest-regex-util	AI (phantom-deps): jest-regex-util is a declared dependency; phantom classification reflects monorepo structure, not a real issue.	ai	2026/04/21
bogus-package	bogus-package	AI (bogus-package): Signals reflect monorepo publishing pattern (coordinated versioning, internal packages); not indicative of spam.	ai	2026/04/21

Versions (showing 49 of 149)

Version	Deps	Published
25.2.0	3 / 3	2020-03-25
25.1.0	3 / 3	2020-01-22
25.0.0	3 / 3	2019-08-22
24.9.0	3 / 3	2019-08-16
24.8.0	3 / 3	2019-05-05
24.7.1	3 / 3	2019-04-04
24.7.0	3 / 3	2019-04-03
24.6.0	3 / 3	2019-04-01
24.5.0	3 / 3	2019-03-12
24.4.0	3 / 3	2019-03-11
24.3.1	3 / 3	2019-03-07
24.3.0	3 / 3	2019-03-07
24.1.0	2 / 0	2019-02-05
24.0.0	2 / 0	2019-01-25
23.6.0	2 / 0	2018-09-10
23.5.0	2 / 0	2018-08-10
23.4.2	2 / 0	2018-07-27
23.4.1	2 / 0	2018-07-13
23.4.0	2 / 0	2018-07-10
23.3.0	2 / 0	2018-07-04
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.3	1 / 0	2018-03-21
22.1.0	1 / 0	2018-01-15
22.0.6	1 / 0	2018-01-11
22.0.5	1 / 0	2018-01-09
22.0.3	1 / 0	2017-12-19
21.2.0	1 / 0	2017-09-26
21.1.0	1 / 0	2017-09-14
21.0.2	1 / 0	2017-09-08
21.0.0	1 / 0	2017-09-04
20.0.3	1 / 0	2017-05-17
20.0.2	1 / 0	2017-05-17
20.0.1	1 / 0	2017-05-11
20.0.0	1 / 0	2017-05-06
19.0.0	1 / 0	2017-02-21
18.1.0	2 / 0	2016-12-29
18.0.0	2 / 0	2016-12-15
17.0.3	2 / 0	2016-11-17
17.0.2	2 / 0	2016-11-15
17.0.1	2 / 0	2016-11-14
17.0.0	2 / 0	2016-11-08
16.0.2	2 / 0	2016-10-20
15.0.1	2 / 0	2016-09-01
15.0.0	2 / 0	2016-08-31
14.1.0	2 / 0	2016-08-01
14.0.0	2 / 0	2016-07-27
0.0.0	0 / 0	2016-07-13

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: scotthovestadt → 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

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-22) provenance

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

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.8.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-05-05) provenance

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

v24.7.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 → scotthovestadt (on 2019-04-04) provenance

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

v24.7.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-04-03) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-04-03. 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.5.0

1 finding

LOW No provenance attestation provenance

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

v24.4.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.1

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

1 finding

LOW No provenance attestation provenance

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

v23.5.0

1 finding

LOW No provenance attestation provenance

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

v23.4.2

1 finding

LOW No provenance attestation provenance

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

v23.4.1

1 finding

LOW No provenance attestation provenance

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

v23.4.0

1 finding

LOW No provenance attestation provenance

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

v23.3.0

1 finding

LOW No provenance attestation provenance

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

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

2 findings

HIGH Publisher changed: cpojer → mjesun (on 2018-03-21) provenance

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

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

2 findings

HIGH Publisher changed: cpojer → mjesun (on 2018-01-09) provenance

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

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.

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.

v21.1.0

1 finding

LOW No provenance attestation provenance

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

v21.0.2

1 finding

LOW No provenance attestation provenance

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

v21.0.0

1 finding

LOW No provenance attestation provenance

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

v20.0.3

1 finding

LOW No provenance attestation provenance

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

v20.0.2

1 finding

LOW No provenance attestation provenance

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

v20.0.1

1 finding

LOW No provenance attestation provenance

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

v20.0.0

1 finding

LOW No provenance attestation provenance

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

v19.0.0

1 finding

LOW No provenance attestation provenance

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

v18.1.0

1 finding

LOW No provenance attestation provenance

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

v18.0.0

1 finding

LOW No provenance attestation provenance

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

v17.0.3

1 finding

LOW No provenance attestation provenance

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

v17.0.2

1 finding

LOW No provenance attestation provenance

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

v17.0.1

1 finding

LOW No provenance attestation provenance

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

v17.0.0

1 finding

LOW No provenance attestation provenance

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

v16.0.2

1 finding

LOW No provenance attestation provenance

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

v15.0.1

1 finding

LOW No provenance attestation provenance

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

v15.0.0

1 finding

LOW No provenance attestation provenance

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

v14.1.0

1 finding

LOW No provenance attestation provenance

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

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

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