tree-sitter-cli
CLI for generating fast incremental parsers
7
Versions
MIT
License
Yes
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
ahlincmaxbrunsfeldamaanqtclemqueervioletrewinfreyrobrixjoshvera
Keywords
parserlexer
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:stackvis | AI (phantom-deps): used conditionally/CLI tooling, stable false positive for this package | ai | |
| dependencies | unvetted-dep:@maxbrunsfeld/flame-graph | AI (dependencies): First-party dep from same maintainer, low risk. | ai | |
| phantom-deps | phantom-dep:nan | AI (phantom-deps): nan is used by node-gyp native build, not imported in JS source. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval used to parse local grammar.json, not remote/untrusted input. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads local grammar module path, standard CLI codegen pattern. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): cli.js uses child_process.spawn solely to invoke the downloaded tree-sitter binary; this is the expected and benign behavior of a CLI wrapper package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Mass-production signal is due to amaanq maintaining many tree-sitter grammar packages (a known ecosystem pattern); no-deps is expected for a prebuilt binary CLI tool. | ai | |
| install-scripts | install-script:install | AI (install-scripts): tree-sitter-cli's install script fetches prebuilt binaries for the target platform — standard pattern for this native CLI tool, consistent across all versions. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.26.9 | 0 / 0 | |
| 0.26.8 | 0 / 0 | |
| 0.26.3 | 0 / 0 | |
| 0.25.4 | 0 / 0 | |
| 0.15.0 | 0 / 0 | |
| 0.10.2 | 9 / 3 | |
| 0.3.0 | 10 / 3 |
v0.15.0
2 findings
HIGH
Missing gitHead — previous versions had it
provenance
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: maxbrunsfeld.
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.