← Home

@vscode/tree-sitter-wasm

npm Repository Homepage
4
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

vscode-botmicrosoft1es

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 4 of 4)

Version Deps Published
0.3.1 0 / 13
0.3.0 0 / 13
0.2.0 0 / 16
0.1.5 0 / 15

v0.3.1

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.

v0.3.0

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.

v0.2.0

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.

v0.1.5

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.