@lezer/python
Lezer-based Python 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@lezer/lr | AI (dependencies): @lezer/lr is a first-party Lezer ecosystem package by the same author (Marijn Haverbeke); not a third-party risk for this package. | ai | |
| source-diff | obfuscated-file:dist/index.js | AI (source-diff): dist/index.js is a lezer-generator output file — generated parser tables with long lines are expected and documented in the build script. Not obfuscation. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @lezer/common is a first-party dependency from the same org/maintainer; adding it is benign for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Lezer ecosystem package by Marijn Haverbeke; inflated semver reflects prior development history, not spam. Short README and no keywords are quality issues only. | ai | |
| phantom-deps | phantom-dep:@lezer/common | AI (phantom-deps): @lezer/common is a legitimate peer/runtime dep in the same org scope; phantom detection is a false positive for this package. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 1.1.19 | 3 / 4 | |
| 1.1.18 | 3 / 4 | |
| 1.1.17 | 3 / 4 | |
| 1.1.16 | 3 / 4 | |
| 1.1.15 | 3 / 4 | |
| 1.1.14 | 3 / 4 | |
| 1.1.13 | 3 / 4 | |
| 1.1.12 | 3 / 4 | |
| 1.1.11 | 3 / 4 | |
| 1.1.10 | 3 / 4 | |
| 1.1.9 | 2 / 4 | |
| 1.1.8 | 2 / 4 | |
| 1.1.7 | 2 / 4 | |
| 1.1.6 | 2 / 4 | |
| 1.1.5 | 2 / 4 | |
| 1.1.4 | 2 / 4 | |
| 1.1.3 | 2 / 4 | |
| 1.1.2 | 2 / 4 | |
| 1.1.1 | 2 / 4 | |
| 1.1.0 | 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.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
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.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.