@codemirror/lang-python
Python language support for the CodeMirror code editor
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:lezer-python | AI (dependencies): lezer-python is Marijn Haverbeke's own parser library, the direct dependency underpinning CodeMirror's language support. Expected and legitimate for this package. | ai | |
| phantom-deps | phantom-dep:@codemirror/state | AI (phantom-deps): @codemirror/state is a standard peer dependency across the entire CodeMirror ecosystem; its presence as a phantom dep is expected and benign for all @codemirror/* packages. | ai | |
| provenance | no-provenance | AI (provenance): Marijn Haverbeke's CodeMirror packages consistently lack Sigstore provenance; this is a stable characteristic of the publisher, not a risk indicator. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 6.2.1 | 5 / 1 | |
| 6.2.0 | 5 / 1 | |
| 6.1.7 | 5 / 1 | |
| 6.1.6 | 5 / 1 | |
| 6.1.5 | 5 / 1 | |
| 6.1.4 | 5 / 1 | |
| 6.1.3 | 3 / 1 | |
| 6.1.2 | 3 / 1 | |
| 6.1.1 | 3 / 1 | |
| 6.1.0 | 3 / 1 | |
| 6.0.4 | 2 / 1 | |
| 6.0.3 | 2 / 1 | |
| 6.0.2 | 2 / 1 | |
| 6.0.1 | 2 / 1 | |
| 6.0.0 | 2 / 1 | |
| 0.20.0 | 2 / 1 | |
| 0.19.5 | 3 / 1 | |
| 0.19.4 | 3 / 1 | |
| 0.19.3 | 3 / 1 | |
| 0.19.2 | 3 / 1 | |
| 0.19.1 | 3 / 1 | |
| 0.19.0 | 3 / 1 | |
| 0.18.1 | 3 / 1 | |
| 0.18.0 | 3 / 3 | |
| 0.17.2 | 3 / 3 | |
| 0.17.1 | 3 / 3 | |
| 0.17.0 | 3 / 3 |
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.