← Home

tree-sitter-json

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

nathansobomaxbrunsfelddaviwilqueervioletben3eeeatom-teamjasonrudolph

Keywords

incrementalparsingtree-sitterjson

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 install script is the standard prebuilt native addon loading pattern for tree-sitter grammar bindings; stable for this package. ai
npm-metadata bundled-binaries AI (npm-metadata): Prebuilt .node binaries for 6 platform/arch combos are the expected prebuildify output for a tree-sitter native addon; stable for this package. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require constructs a path to the correct platform-specific prebuilt binary — a well-understood pattern for native addons, not arbitrary module loading. ai
phantom-deps phantom-dep:node-addon-api AI (phantom-deps): node-addon-api is used in binding.gyp for native compilation, not imported in JS — this is the correct usage pattern for native addon headers. ai

Versions (showing 1 of 1)

Version Deps Published
0.24.8 2 / 4

v0.24.8

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-json.node • prebuilds/darwin-x64/tree-sitter-json.node • prebuilds/linux-arm64/tree-sitter-json.node • prebuilds/linux-x64/tree-sitter-json.node • prebuilds/win32-arm64/tree-sitter-json.node • prebuilds/win32-x64/tree-sitter-json.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.