jest-config
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-peer-dep:ts-node | AI (dependencies): ts-node is an optional peer dependency; unvetted status is acceptable for optional tooling. | ai | |
| source-diff | large-new-source-files | AI (source-diff): 26 new files consistent with Jest monorepo development; no obfuscation or malware indicators. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): cpojer removal is normal Jest team evolution; package remains under official Facebook/Jest org with active maintainer. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Jest monorepo maintainer transition; rubennorte and scotthovestadt are documented Jest maintainers. | ai | |
| phantom-deps | phantom-dep:babel-core | AI (phantom-deps): babel-core is referenced as a default transformer string in config, not directly imported — this is the expected usage pattern for jest-config. | ai | |
| provenance | no-provenance | AI (provenance): Provenance is a best-practice gap; not a blocker for packages with strong ecosystem trust. | ai | |
| dependencies | unvetted-dep:babel-core | AI (dependencies): babel-core is a well-known Babel v6 package legitimately added in Jest 23 as a required peer for the default babel-jest transformer. Not a supply chain risk. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change (mjesun → scotthovestadt) occurred in 2019 as documented Jest maintainer transition. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are Jest-scoped or established packages (micromatch, @babel/core, realpath-native); appropriate for config module. | ai | |
| source-diff | obfuscated-file:build/normalize.js | AI (source-diff): build/normalize.js is a standard Babel-compiled build artifact from the facebook/jest monorepo, not malicious obfuscation. Pattern is consistent across all Jest package builds. | ai | |
| phantom-deps | phantom-dep:jest-mock | AI (phantom-deps): jest-mock is referenced as a default config value resolved at runtime. Phantom-dep pattern is expected and stable for jest-config. | ai | |
| phantom-deps | phantom-dep:json-stable-stringify | AI (phantom-deps): json-stable-stringify is a runtime-resolved dependency used via configuration, not direct import. Expected pattern for jest-config. | ai | |
| phantom-deps | phantom-dep:jest-environment-jsdom | AI (phantom-deps): Referenced in config files; expected phantom dep for Jest config module. | ai | |
| dependencies | unvetted-dep:jest-jasmine2 | AI (dependencies): jest-jasmine2 is a sibling package in the same Jest monorepo; internal dependency is safe. | ai | |
| phantom-deps | phantom-dep:istanbul | AI (phantom-deps): jest-config passes istanbul as a default coverage provider via configuration strings resolved at runtime, not via direct import. This phantom-dep pattern is stable for this package. | ai | |
| dependencies | unvetted-dep:@jest/test-sequencer | AI (dependencies): @jest/test-sequencer is a first-party Jest monorepo sibling, co-released at the same version. Not a third-party risk. | ai | |
| dependencies | unvetted-dep:jest-circus | AI (dependencies): jest-circus is a first-party Jest monorepo sibling, co-released at the same version. Not a third-party risk. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): jest-config 0.0.0 is a namespace reservation by the core Jest maintainer (cpojer). The 0.0.0 version is intentional and not indicative of malicious intent for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): jest-config is a monorepo package; missing description is common in Jest's published structure. | ai | |
| phantom-deps | phantom-dep:@jest/test-sequencer | AI (phantom-deps): Jest-scoped package loaded by convention; expected in config module. | ai | |
| phantom-deps | phantom-dep:jest-environment-node | AI (phantom-deps): Referenced in config files; expected phantom dep for Jest config module. | ai | |
| bogus-package | bogus-package | AI (bogus-package): jest-config is a Jest monorepo package following unified versioning (30.x). Inflated semver, no description, and no keywords are expected for this monorepo package — not spam indicators. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Framework-scoped package loaded by convention in Jest's build pipeline. | ai | |
| phantom-deps | phantom-dep:jest-runner | AI (phantom-deps): jest-config references jest-runner as the default test runner via config; loaded by convention, not direct import. | ai |
Versions (showing 87 of 187)
| Version | Deps | Published |
|---|---|---|
| 25.2.3 | 18 / 3 | |
| 25.2.2 | 18 / 3 | |
| 25.2.1 | 18 / 3 | |
| 25.2.0 | 18 / 3 | |
| 25.1.0 | 17 / 3 | |
| 25.0.0 | 17 / 3 | |
| 24.9.0 | 17 / 3 | |
| 24.8.0 | 17 / 3 | |
| 24.7.1 | 17 / 3 | |
| 24.7.0 | 17 / 3 | |
| 24.6.0 | 16 / 3 | |
| 24.5.0 | 16 / 3 | |
| 24.4.0 | 16 / 3 | |
| 24.3.1 | 16 / 3 | |
| 24.3.0 | 16 / 3 | |
| 24.1.0 | 15 / 0 | |
| 24.0.0 | 16 / 0 | |
| 23.6.0 | 14 / 0 | |
| 23.5.0 | 14 / 0 | |
| 23.4.2 | 13 / 0 | |
| 23.4.1 | 13 / 0 | |
| 23.4.0 | 13 / 0 | |
| 23.3.0 | 13 / 0 | |
| 23.2.0 | 13 / 0 | |
| 23.1.0 | 13 / 0 | |
| 23.0.0 | 13 / 0 | |
| 22.4.4 | 11 / 0 | |
| 22.4.3 | 11 / 0 | |
| 22.4.2 | 11 / 0 | |
| 22.4.1 | 11 / 0 | |
| 22.4.0 | 11 / 0 | |
| 22.3.0 | 11 / 0 | |
| 22.2.2 | 11 / 0 | |
| 22.2.1 | 11 / 0 | |
| 22.2.0 | 11 / 0 | |
| 22.1.4 | 11 / 0 | |
| 22.1.3 | 11 / 0 | |
| 22.1.2 | 11 / 0 | |
| 22.1.1 | 11 / 0 | |
| 22.1.0 | 11 / 0 | |
| 22.0.6 | 11 / 0 | |
| 22.0.5 | 11 / 0 | |
| 22.0.4 | 11 / 0 | |
| 22.0.3 | 11 / 0 | |
| 22.0.2 | 11 / 0 | |
| 22.0.1 | 11 / 0 | |
| 22.0.0 | 11 / 0 | |
| 21.2.1 | 11 / 0 | |
| 21.2.0 | 11 / 0 | |
| 21.1.0 | 11 / 0 | |
| 21.0.2 | 11 / 0 | |
| 21.0.0 | 11 / 0 | |
| 20.0.4 | 10 / 0 | |
| 20.0.3 | 10 / 0 | |
| 20.0.2 | 10 / 0 | |
| 20.0.1 | 10 / 0 | |
| 20.0.0 | 9 / 0 | |
| 19.0.4 | 8 / 0 | |
| 19.0.3 | 8 / 0 | |
| 19.0.2 | 8 / 0 | |
| 19.0.1 | 8 / 0 | |
| 19.0.0 | 8 / 0 | |
| 18.1.0 | 8 / 0 | |
| 18.0.0 | 8 / 0 | |
| 17.0.3 | 9 / 0 | |
| 17.0.2 | 9 / 0 | |
| 17.0.1 | 9 / 0 | |
| 17.0.0 | 9 / 0 | |
| 16.0.2 | 9 / 0 | |
| 16.0.0 | 9 / 0 | |
| 15.1.1 | 9 / 0 | |
| 15.1.0 | 9 / 0 | |
| 15.0.1 | 9 / 0 | |
| 15.0.0 | 9 / 0 | |
| 14.1.0 | 9 / 0 | |
| 14.0.1 | 9 / 0 | |
| 14.0.0 | 9 / 0 | |
| 13.2.3 | 11 / 0 | |
| 13.2.2 | 11 / 0 | |
| 13.2.1 | 11 / 0 | |
| 13.2.0 | 11 / 0 | |
| 13.1.3 | 11 / 0 | |
| 13.1.2 | 11 / 0 | |
| 13.1.1 | 11 / 0 | |
| 13.1.0 | 11 / 0 | |
| 13.0.0 | 11 / 0 | |
| 0.0.0 | 0 / 0 |
v25.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.7.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.3.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-03-07. This could indicate a legitimate maintainer transition or an account compromise.
v24.1.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.4.4
1 finding[Accepted risk] 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[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.0.4
2 findingsThis version was published by a different npm account than previous versions on 2017-12-22. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.