@lezer/rust
Lezer-based Rust grammar
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index.js | AI (source-diff): dist/index.js is a lezer-generator + rollup build artifact. Long lines are bundled parser tables/logic, not obfuscation. This is the standard distribution pattern for all @lezer/* packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Focused parser library in the lezer ecosystem; minimal README and no keywords are consistent with the package's narrow, well-defined purpose. | ai | |
| phantom-deps | phantom-dep:@lezer/common | AI (phantom-deps): @lezer/common is a legitimate peer/runtime dep in the Lezer ecosystem; not being directly imported in the detected sense is expected for grammar packages exposing types. | ai | |
| typosquat | typosquat.levenshtein:nuxt | AI (typosquat): @lezer/rust is a scoped Lezer parser package with no relation to nuxt; Levenshtein distance match is a clear false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): @lezer/rust is a scoped Lezer parser package with no relation to jest; Levenshtein distance match is a clear false positive for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.0.2 | 3 / 4 | |
| 1.0.1 | 2 / 4 | |
| 1.0.0 | 2 / 4 | |
| 0.16.1 | 2 / 4 | |
| 0.16.0 | 2 / 4 | |
| 0.15.1 | 1 / 4 | |
| 0.15.0 | 1 / 4 |
v1.0.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.