lezer-json
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transfer from satchmorun to marijn (Marijn Haverbeke) is a documented, legitimate handoff within the lezer-parser ecosystem. Marijn is the canonical maintainer of all lezer packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): marijn is the well-established steward of the lezer ecosystem; this addition reflects the legitimate transfer of the lezer-json package to its canonical maintainer. | ai | |
| bogus-package | bogus-package | AI (bogus-package): lezer-json is a legitimate grammar package in the lezer-parser org. Sparse README and missing keywords are cosmetic, not security-relevant. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.13.2 | 1 / 4 | |
| 0.13.1 | 1 / 4 | |
| 0.13.0 | 1 / 4 | |
| 0.12.0 | 1 / 4 | |
| 0.11.1 | 1 / 4 | |
| 0.11.0 | 1 / 4 | |
| 0.10.0 | 1 / 4 | |
| 0.8.5 | 1 / 7 | |
| 0.8.4 | 1 / 7 | |
| 0.1.1 | 1 / 7 | |
| 0.1.0 | 1 / 4 |
v0.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.1
2 findingsThis version was published by a different npm account than previous versions on 2020-12-04. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
2 findingsThis version was published by a different npm account than previous versions on 2020-12-04. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
2 findingsThis version was published by a different npm account than previous versions on 2020-10-23. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
2 findingsThis version was published by a different npm account than previous versions on 2020-09-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
2 findingsThis version was published by a different npm account than previous versions on 2020-09-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
2 findingsThis version was published by a different npm account than previous versions on 2020-09-23. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.