@codemirror/lang-javascript
JavaScript 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@codemirror/state | AI (phantom-deps): @codemirror/state is explicitly declared as a dependency in package.json and is a same-org sibling package; phantom-dep detection is a false positive for this package. | ai | |
| dependencies | unvetted-dep:lezer-javascript | AI (dependencies): lezer-javascript is the official Lezer JS parser by the same author (Marijn Haverbeke) and a core CodeMirror ecosystem dependency; stable legitimate dependency. | ai | |
| provenance | no-provenance | AI (provenance): Official CodeMirror package by Marijn Haverbeke; lack of Sigstore provenance is common and not a meaningful risk signal for this well-established author. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 6.2.5 | 7 / 2 | |
| 6.2.4 | 7 / 2 | |
| 6.2.3 | 7 / 2 | |
| 6.2.2 | 7 / 2 | |
| 6.2.1 | 7 / 2 | |
| 6.2.0 | 7 / 2 | |
| 6.1.9 | 7 / 2 | |
| 6.1.8 | 7 / 2 | |
| 6.1.7 | 7 / 2 | |
| 6.1.6 | 7 / 2 | |
| 6.1.5 | 7 / 2 | |
| 6.1.4 | 7 / 2 | |
| 6.1.3 | 7 / 2 | |
| 6.1.2 | 7 / 2 | |
| 6.1.1 | 7 / 2 | |
| 6.1.0 | 7 / 2 | |
| 6.0.2 | 7 / 2 | |
| 6.0.1 | 7 / 2 | |
| 6.0.0 | 7 / 2 | |
| 0.20.1 | 7 / 2 | |
| 0.20.0 | 6 / 2 | |
| 0.19.7 | 7 / 2 | |
| 0.19.6 | 7 / 2 | |
| 0.19.5 | 7 / 2 | |
| 0.19.4 | 7 / 2 | |
| 0.19.3 | 7 / 2 | |
| 0.19.2 | 7 / 2 | |
| 0.19.1 | 7 / 2 | |
| 0.19.0 | 7 / 2 | |
| 0.18.0 | 7 / 7 | |
| 0.17.2 | 7 / 7 | |
| 0.17.1 | 7 / 7 | |
| 0.17.0 | 7 / 7 |
v6.2.4
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.2.3
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.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.6
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.