tree-sitter-c
6
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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
ahlincmaxbrunsfeldamaanqtclemdaviwilrewinfreyjoshveraatom-teampatrickthomson
Keywords
incrementalparsingtree-sitterc
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Trusted long-running maintainer; grammar packages publish infrequently between tree-sitter-cli updates. | ai | |
| 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 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.24.1 | 2 / 4 | |
| 0.24.0 | 2 / 4 | |
| 0.23.6 | 2 / 4 | |
| 0.23.3 | 2 / 4 | |
| 0.23.2 | 2 / 4 | |
| 0.21.3 | 2 / 4 |
v0.23.3
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.3
1 finding
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.