tree-sitter-bash
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 used at build time via binding.gyp, not directly imported in JS; stable false positive for native addons. | ai | |
| install-scripts | install-script:install | AI (install-scripts): node-gyp-build install script is the standard pattern for native addons shipping prebuilts; stable and expected for this package. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Prebuilt .node binaries for multiple platforms are the expected output of prebuildify for a tree-sitter grammar binding; not a backdoor risk. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require constructs platform/arch path to load bundled prebuilt binary — fully deterministic and safe, not arbitrary module loading. | ai |
v0.25.1
3 findingsScript: node-gyp-build
Package contains compiled binaries that could be backdoors: • prebuilds/darwin-arm64/tree-sitter-bash.node • prebuilds/darwin-x64/tree-sitter-bash.node • prebuilds/linux-arm64/tree-sitter-bash.node • prebuilds/linux-x64/tree-sitter-bash.node • prebuilds/win32-arm64/tree-sitter-bash.node • prebuilds/win32-x64/tree-sitter-bash.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.