tree-sitter-c
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:node-addon-api | AI (phantom-deps): node-addon-api is a build-time native binding dep referenced in binding.gyp, not imported in JS; stable false positive. | ai | |
| install-scripts | install-script:install | AI (install-scripts): node-gyp-build is the standard install script for native Node.js addons shipping prebuilts; stable and expected for this package. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Prebuilt .node binaries for 3 platforms × 2 arches are the expected artifact for a native tree-sitter grammar; source and binding.gyp are also included. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used only to load the platform-specific prebuild .node file; a well-understood, benign native addon loading pattern. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.24.1 | 2 / 4 | |
| 0.24.0 | 2 / 4 | |
| 0.23.6 | 2 / 4 | |
| 0.23.2 | 2 / 4 |
v0.24.1
3 findingsScript: node-gyp-build
Package contains compiled binaries that could be backdoors: • prebuilds/darwin-arm64/tree-sitter-c.node • prebuilds/darwin-x64/tree-sitter-c.node • prebuilds/linux-arm64/tree-sitter-c.node • prebuilds/linux-x64/tree-sitter-c.node • prebuilds/win32-arm64/tree-sitter-c.node • prebuilds/win32-x64/tree-sitter-c.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.2
3 findingsScript: node-gyp-build
Package contains compiled binaries that could be backdoors: • prebuilds/darwin-arm64/tree-sitter-c.node • prebuilds/darwin-x64/tree-sitter-c.node • prebuilds/linux-arm64/tree-sitter-c.node • prebuilds/linux-x64/tree-sitter-c.node • prebuilds/win32-arm64/tree-sitter-c.node • prebuilds/win32-x64/tree-sitter-c.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.