@vscode/tree-sitter-wasm
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): Prebuilt tree-sitter WASM is the package's stated purpose. | ai | |
| semgrep | semgrep:toplevel-fetch | AI (semgrep): fetch() in tree-sitter.js is the standard Emscripten/WASM loader pattern for fetching the .wasm binary in browser environments; not telemetry or exfiltration. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval() is inside Emscripten's addEmAsm() runtime helper for EM_ASM blocks; standard generated code in any Emscripten-compiled WASM JS wrapper. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Microsoft-scoped WASM binary package; README linking to upstream Tree-Sitter project is expected. Not spam or phishing. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.3.1 | 0 / 13 | |
| 0.3.0 | 0 / 13 | |
| 0.2.0 | 0 / 16 | |
| 0.1.5 | 0 / 15 | |
| 0.1.4 | 0 / 14 | |
| 0.1.3 | 0 / 13 | |
| 0.1.2 | 0 / 13 | |
| 0.1.1 | 0 / 13 | |
| 0.1.0 | 0 / 13 | |
| 0.0.5 | 0 / 13 | |
| 0.0.4 | 0 / 5 | |
| 0.0.3 | 0 / 4 | |
| 0.0.2 | 0 / 4 | |
| 0.0.1 | 0 / 4 |
v0.1.4
2 findingsPackage contains compiled binaries that could be backdoors: • wasm/tree-sitter-c-sharp.wasm • wasm/tree-sitter-cpp.wasm • wasm/tree-sitter-css.wasm • wasm/tree-sitter-go.wasm • wasm/tree-sitter-ini.wasm • wasm/tree-sitter-java.wasm • wasm/tree-sitter-javascript.wasm • wasm/tree-sitter-python.wasm • wasm/tree-sitter-regex.wasm • wasm/tree-sitter-ruby.wasm ... and 4 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
2 findingsPackage contains compiled binaries that could be backdoors: • wasm/tree-sitter-c-sharp.wasm • wasm/tree-sitter-cpp.wasm • wasm/tree-sitter-go.wasm • wasm/tree-sitter-ini.wasm • wasm/tree-sitter-java.wasm • wasm/tree-sitter-javascript.wasm • wasm/tree-sitter-python.wasm • wasm/tree-sitter-regex.wasm • wasm/tree-sitter-ruby.wasm • wasm/tree-sitter-rust.wasm ... and 3 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
2 findingsPackage contains compiled binaries that could be backdoors: • wasm/tree-sitter-c-sharp.wasm • wasm/tree-sitter-cpp.wasm • wasm/tree-sitter-go.wasm • wasm/tree-sitter-ini.wasm • wasm/tree-sitter-java.wasm • wasm/tree-sitter-javascript.wasm • wasm/tree-sitter-python.wasm • wasm/tree-sitter-regex.wasm • wasm/tree-sitter-ruby.wasm • wasm/tree-sitter-rust.wasm ... and 3 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
2 findingsPackage contains compiled binaries that could be backdoors: • wasm/tree-sitter-c-sharp.wasm • wasm/tree-sitter-cpp.wasm • wasm/tree-sitter-go.wasm • wasm/tree-sitter-java.wasm • wasm/tree-sitter-javascript.wasm • wasm/tree-sitter-python.wasm • wasm/tree-sitter-regex.wasm • wasm/tree-sitter-ruby.wasm • wasm/tree-sitter-rust.wasm • wasm/tree-sitter-tsx.wasm ... and 2 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
2 findingsPackage contains compiled binaries that could be backdoors: • wasm/tree-sitter-c-sharp.wasm • wasm/tree-sitter-cpp.wasm • wasm/tree-sitter-go.wasm • wasm/tree-sitter-java.wasm • wasm/tree-sitter-javascript.wasm • wasm/tree-sitter-python.wasm • wasm/tree-sitter-regex.wasm • wasm/tree-sitter-ruby.wasm • wasm/tree-sitter-rust.wasm • wasm/tree-sitter-tsx.wasm ... and 2 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
2 findingsPackage contains compiled binaries that could be backdoors: • wasm/tree-sitter-c-sharp.wasm • wasm/tree-sitter-cpp.wasm • wasm/tree-sitter-go.wasm • wasm/tree-sitter-java.wasm • wasm/tree-sitter-javascript.wasm • wasm/tree-sitter-python.wasm • wasm/tree-sitter-regex.wasm • wasm/tree-sitter-ruby.wasm • wasm/tree-sitter-rust.wasm • wasm/tree-sitter-tsx.wasm ... and 2 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
2 findingsPackage contains compiled binaries that could be backdoors: • wasm/tree-sitter-regex.wasm • wasm/tree-sitter-typescript.wasm • wasm/tree-sitter.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
2 findingsPackage contains compiled binaries that could be backdoors: • wasm/tree-sitter-typescript.wasm • wasm/tree-sitter.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
2 findingsPackage contains compiled binaries that could be backdoors: • wasm/tree-sitter-typescript.wasm • wasm/tree-sitter.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
2 findingsPackage contains compiled binaries that could be backdoors: • wasm/tree-sitter-typescript.wasm • wasm/tree-sitter.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.