@ast-grep/cli
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established high-download package with 167 versions; gap likely reflects release cadence, not takeover. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall selects platform-specific prebuilt binary from optional deps — standard native binary distribution pattern, stable for this package. | ai | |
| dependencies | unvetted-dep:detect-libc | AI (dependencies): detect-libc is a well-known utility for detecting Linux C library variant; its use here is expected for selecting the correct native binary optional dependency. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @ast-grep/cli is a long-established AST tool with no relation to joi; Levenshtein distance match is a false positive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Tiny payload and minimal README are expected for a binary wrapper package; actual binaries live in platform-specific optional dependency packages. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.42.3 | 1 / 0 | |
| 0.42.2 | 1 / 0 | |
| 0.42.1 | 1 / 0 | |
| 0.39.7 | 1 / 0 | |
| 0.38.2 | 1 / 0 | |
| 0.38.1 | 1 / 0 | |
| 0.38.0 | 1 / 0 |
v0.42.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.1
2 findingsScript: node postinstall.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.39.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.