tree-sitter
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require constructs a platform/arch path to load the native .node addon — standard pattern for native bindings, not a supply-chain risk. | ai | |
| dependencies | unvetted-dep:node-gyp-build | AI (dependencies): node-gyp-build is the standard native addon binary loader; its use here is expected and appropriate. | ai | |
| install-scripts | install-script:install | AI (install-scripts): node-gyp-build is the canonical install script for native Node.js addons shipping prebuilts; stable and expected for tree-sitter across all versions. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Prebuilt .node binaries for major platforms are the documented output of prebuildify; expected for this native addon package. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval() is used to create dynamically-named SyntaxNode subclasses from grammar type names — a legitimate pattern, not external input. Not a supply-chain risk. | ai | |
| phantom-deps | phantom-dep:node-addon-api | AI (phantom-deps): node-addon-api is referenced in binding.gyp for native compilation, not JS imports — standard N-API addon pattern. | ai |
v0.25.0
2 findingsScript: node-gyp-build
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.1
3 findingsScript: node-gyp-build
Package contains compiled binaries that could be backdoors: • prebuilds/darwin-arm64/tree-sitter.node • prebuilds/darwin-x64/tree-sitter.node • prebuilds/linux-x64/tree-sitter.node • prebuilds/win32-x64/tree-sitter.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.