@unit-mesh/treesitter-artifacts
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | url-dep:tree-sitter-vue | AI (npm-metadata): devDependency only; used to build WASM artifacts not shipped to consumers. SHA-pin is a supply-chain hygiene measure, not an attack vector here. | ai | |
| npm-metadata | url-dep:tree-sitter-go | AI (npm-metadata): devDependency only; build-time grammar source, not shipped to consumers. | ai | |
| npm-metadata | url-dep:tree-sitter-cpp | AI (npm-metadata): devDependency only; build-time grammar source, not shipped to consumers. | ai | |
| npm-metadata | url-dep:tree-sitter-zig | AI (npm-metadata): devDependency only; build-time grammar source, not shipped to consumers. | ai | |
| npm-metadata | url-dep:tree-sitter-cobol | AI (npm-metadata): devDependency only; build-time grammar source, not shipped to consumers. | ai | |
| npm-metadata | url-dep:tree-sitter-typescript | AI (npm-metadata): devDependency only; build-time grammar source, not shipped to consumers. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.7.7 | 0 / 32 |
v1.7.7
2 findingsDependency 'tree-sitter-vue' in `devDependencies` points to 'git+https://github.com/tree-sitter-grammars/tree-sitter-vue.git#7e48557b903a9db9c38cea3b7839ef7e1f36c693' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.