estree-walk
Walk ESTree nodes simple and fast
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Package is ~10 years old, predates Sigstore provenance. No other risk signals; absence of provenance is expected for this era of package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.2.0 | 0 / 5 | |
| 2.1.0 | 0 / 4 | |
| 1.1.0 | 1 / 4 | |
| 1.0.0 | 1 / 4 | |
| 0.3.2 | 1 / 3 | |
| 0.3.1 | 1 / 2 | |
| 0.3.0 | 1 / 2 | |
| 0.2.2 | 1 / 2 | |
| 0.2.1 | 1 / 2 | |
| 0.2.0 | 1 / 2 | |
| 0.1.1 | 1 / 2 | |
| 0.1.0 | 1 / 2 | |
| 0.0.0 | 1 / 2 |
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.