← Home

tree-sitter-ruby

1
Versions
License
Yes
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

amaanqahlincmaxbrunsfeldnathansobotclemdaviwilqueervioletrewinfreyjoshveraatom-teamjasonrudolphpatrickthomson

Keywords

incrementalparsingtree-sitterruby

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:install AI (install-scripts): node-gyp-build is the standard install pattern for native Node.js addons; stable and expected for tree-sitter-ruby across all versions. ai
npm-metadata bundled-binaries AI (npm-metadata): Prebuilt .node files for 6 platform/arch combos are the documented prebuildify distribution pattern for tree-sitter grammar packages. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require constructs a deterministic path from process.platform/arch to load the correct prebuilt binary — not arbitrary code loading. ai
phantom-deps phantom-dep:node-addon-api AI (phantom-deps): node-addon-api is a build-time dependency used via binding.gyp, not directly imported in JS. Standard pattern for native addons. ai

Versions (showing 1 of 1)

Version Deps Published
0.23.1 2 / 4

v0.23.1

3 findings
HIGH Package has 'install' script install-scripts

Script: node-gyp-build

HIGH Bundled binary files (6) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/darwin-arm64/tree-sitter-ruby.node • prebuilds/darwin-x64/tree-sitter-ruby.node • prebuilds/linux-arm64/tree-sitter-ruby.node • prebuilds/linux-x64/tree-sitter-ruby.node • prebuilds/win32-arm64/tree-sitter-ruby.node • prebuilds/win32-x64/tree-sitter-ruby.node

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.