node-haste
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-dep:esprima-fb | AI (dependencies): esprima-fb is Facebook's well-known esprima fork, an expected and stable dependency for node-haste's JS parsing functionality. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in ResourceLoader is a standard plugin-loader pattern for this build tool; not a security risk in context. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): cpojer is a well-known Meta/Facebook engineer; this is a legitimate maintainer transition, not a takeover. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from cpojer to davidaurelio occurred in 2016; both are known Meta/Facebook engineers. davidaurelio has 132 approved packages. This is a stable historical transition, not a compromise. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): node-haste is a file-watching/module resolution tool; child_process use for OS interaction (e.g., watchman detection) is expected and documented behavior. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Flagged maintainers (zpao, jeffmo, leebyron, cpojer) are well-known Meta/Facebook open source engineers, not spam publishers. False positive for this package. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 2.12.0 | 6 / 10 | |
| 2.11.0 | 6 / 10 | |
| 2.10.1 | 7 / 10 | |
| 2.10.0 | 7 / 10 | |
| 2.9.6 | 7 / 10 | |
| 2.9.5 | 7 / 10 | |
| 2.9.4 | 7 / 10 | |
| 2.9.3 | 7 / 10 | |
| 2.9.2 | 7 / 9 | |
| 2.9.0 | 7 / 9 | |
| 2.8.0 | 7 / 9 | |
| 2.7.0 | 7 / 9 | |
| 2.6.1 | 7 / 9 | |
| 2.6.0 | 7 / 9 | |
| 2.5.0 | 7 / 9 | |
| 2.4.0 | 8 / 9 | |
| 2.3.0 | 8 / 9 | |
| 2.2.0 | 8 / 9 | |
| 2.1.3 | 8 / 9 | |
| 2.1.2 | 8 / 9 | |
| 2.1.1 | 8 / 9 | |
| 2.1.0 | 8 / 9 | |
| 2.0.0 | 7 / 9 | |
| 1.2.6 | 1 / 1 | |
| 1.2.5 | 1 / 0 | |
| 1.2.1 | 1 / 0 | |
| 0.2.1 | 1 / 0 | |
| 0.2.0 | 1 / 0 |
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.6
2 findingsThis version was published by a different npm account than previous versions on 2016-04-06. 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.
v2.9.5
2 findingsThis version was published by a different npm account than previous versions on 2016-04-06. 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.
v2.9.4
2 findingsThis version was published by a different npm account than previous versions on 2016-03-23. 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.
v2.9.3
2 findingsThis version was published by a different npm account than previous versions on 2016-03-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.
v2.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
2 findingsThis version was published by a different npm account than previous versions on 2016-03-09. 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.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
2 findingsThis version was published by a different npm account than previous versions on 2016-03-05. 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.
v2.5.0
2 findingsThis version was published by a different npm account than previous versions on 2016-02-26. 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.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
2 findingsThis version was published by a different npm account than previous versions on 2016-02-20. 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.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
2 findingsThis version was published by a different npm account than previous versions on 2016-02-19. 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.
v2.1.1
2 findingsThis version was published by a different npm account than previous versions on 2016-02-18. 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.
v2.1.0
2 findingsThis version was published by a different npm account than previous versions on 2016-02-18. 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.
v2.0.0
2 findingsThis version was published by a different npm account than previous versions on 2016-02-17. 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.
v1.2.6
2 findingsPackage 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 2014-07-03. This could indicate a legitimate maintainer transition or an account compromise.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.