jest-haste-map
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 |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): jest-haste-map is a core Jest package; large file additions are expected across major version bumps (e.g., 24.x series refactors and TypeScript type additions). No malicious content indicated. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is in a test file mocking worker farm behavior — standard Jest test pattern, not a runtime risk for consumers. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process import is in test files for the node crawler; expected behavior for testing filesystem crawling utilities. | ai | |
| provenance | publisher-changed | AI (provenance): simenb is a well-known Jest core maintainer at Facebook; the cpojer→simenb transition is a documented Jest team handoff, not a compromise. | ai | |
| provenance | no-provenance | AI (provenance): Provenance attestation is absent on ~88% of npm packages; not a material risk for established packages with strong publisher history. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): jest-docblock is a first-party Jest package versioned in lockstep (^20.0.0); not a suspicious third-party dependency. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): davidaurelio is a known Facebook/Jest contributor; maintainer rotation in the Jest monorepo is expected and not a takeover signal. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): gaearon and kentaromiura stepping back from jest-haste-map is consistent with normal team evolution at Facebook; no hostile takeover indicators. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Package is a 10-year-old namespace reservation by trusted Jest maintainer cpojer; 0.0.0 is a historical placeholder, not a malicious pattern. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo packages often omit descriptions; not indicative of malice in this context. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is a framework-scoped type package; expected for Node.js utilities. | ai | |
| phantom-deps | phantom-dep:@types/graceful-fs | AI (phantom-deps): @types/graceful-fs is intentionally listed as a runtime dep in Jest packages to provide types to consumers; standard Jest monorepo pattern. | ai | |
| dependencies | unvetted-dep:@types/graceful-fs | AI (dependencies): @types/graceful-fs is a DefinitelyTyped type-only package with no runtime code; negligible risk for this well-known Jest package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Signals are false positives for monorepo packages versioned to match Jest's release cycle (30.3.0), not inflated semver on a new package. | ai | |
| dependencies | unvetted-dep:fb-watchman | AI (dependencies): fb-watchman is Facebook's file-system watcher; core dependency for jest-haste-map's caching strategy. | ai | |
| dependencies | unvetted-dep:jest-regex-util | AI (dependencies): jest-regex-util is an internal Jest package; appropriate internal dependency. | ai | |
| dependencies | unvetted-dep:walker | AI (dependencies): walker is a legitimate file-system traversal library; appropriate for jest-haste-map's file-hashing use case. | ai |
Versions (showing 51 of 149)
| Version | Deps | Published |
|---|---|---|
| 30.4.1 | 10 / 4 | |
| 30.4.0 | 10 / 4 | |
| 30.3.0 | 10 / 4 | |
| 30.2.0 | 10 / 4 | |
| 30.1.0 | 10 / 4 | |
| 30.0.5 | 10 / 4 | |
| 30.0.2 | 10 / 4 | |
| 30.0.1 | 10 / 4 | |
| 30.0.0 | 10 / 4 | |
| 29.7.0 | 12 / 3 | |
| 29.6.4 | 12 / 3 | |
| 29.6.3 | 12 / 3 | |
| 29.6.2 | 12 / 3 | |
| 29.6.1 | 12 / 3 | |
| 29.6.0 | 12 / 3 | |
| 29.5.0 | 12 / 3 | |
| 29.4.3 | 12 / 3 | |
| 29.4.2 | 12 / 3 | |
| 29.4.1 | 12 / 4 | |
| 29.4.0 | 12 / 4 | |
| 29.3.1 | 12 / 4 | |
| 29.3.0 | 12 / 4 | |
| 29.2.1 | 12 / 4 | |
| 29.2.0 | 12 / 4 | |
| 29.1.2 | 12 / 4 | |
| 29.1.0 | 12 / 4 | |
| 29.0.3 | 12 / 4 | |
| 29.0.2 | 12 / 4 | |
| 29.0.1 | 12 / 4 | |
| 29.0.0 | 12 / 4 | |
| 28.1.3 | 12 / 4 | |
| 28.1.1 | 12 / 4 | |
| 28.1.0 | 12 / 4 | |
| 28.0.2 | 12 / 4 | |
| 28.0.1 | 12 / 4 | |
| 28.0.0 | 12 / 4 | |
| 27.5.1 | 13 / 4 | |
| 27.5.0 | 13 / 5 | |
| 27.4.6 | 13 / 5 | |
| 27.4.5 | 13 / 5 | |
| 27.4.4 | 13 / 5 | |
| 27.4.2 | 13 / 5 | |
| 27.4.1 | 13 / 5 | |
| 27.4.0 | 13 / 5 | |
| 27.3.1 | 13 / 5 | |
| 27.3.0 | 13 / 5 | |
| 27.2.5 | 13 / 5 | |
| 27.2.4 | 13 / 5 | |
| 27.2.3 | 13 / 5 | |
| 27.2.2 | 13 / 5 | |
| 27.2.0 | 13 / 5 |
v30.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.4.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 2026-05-07. This could indicate a legitimate maintainer transition or an account compromise.
v30.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.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 2022-04-25. This could indicate a legitimate maintainer transition or an account compromise.
v27.5.1
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 2022-02-08. This could indicate a legitimate maintainer transition or an account compromise.
v27.5.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 2022-02-05. This could indicate a legitimate maintainer transition or an account compromise.
v27.4.6
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 2022-01-04. This could indicate a legitimate maintainer transition or an account compromise.
v27.4.5
2 findingsThis version was published by a different npm account than previous versions on 2021-12-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.4
2 findingsThis version was published by a different npm account than previous versions on 2021-12-10. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.2
2 findingsThis version was published by a different npm account than previous versions on 2021-11-30. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.1
2 findingsThis version was published by a different npm account than previous versions on 2021-11-30. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.0
2 findingsThis version was published by a different npm account than previous versions on 2021-11-29. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.3.1
2 findingsThis version was published by a different npm account than previous versions on 2021-10-19. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.3.0
2 findingsThis version was published by a different npm account than previous versions on 2021-10-17. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.5
2 findingsThis version was published by a different npm account than previous versions on 2021-10-08. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.4
2 findingsThis version was published by a different npm account than previous versions on 2021-09-29. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.3
2 findingsThis version was published by a different npm account than previous versions on 2021-09-28. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.2
2 findingsThis version was published by a different npm account than previous versions on 2021-09-25. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.0
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.