@codemirror/lang-json
JSON 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:lezer-tree | AI (phantom-deps): lezer-tree is a legitimate peer/type dependency of this CodeMirror package, referenced in config but not directly imported. No security risk. | ai | |
| dependencies | unvetted-dep:lezer-json | AI (dependencies): lezer-json is the expected JSON parser dependency for this CodeMirror language package; legitimate and expected for this ecosystem. | ai | |
| dependencies | unvetted-dep:@codemirror/language | AI (dependencies): @codemirror/language is a core CodeMirror 6 package by the same author (Marijn Haverbeke); it is a legitimate and expected dependency for all @codemirror/lang-* packages. | ai | |
| dependencies | unvetted-dep:@lezer/json | AI (dependencies): @lezer/json is the official Lezer JSON grammar maintained by the same author (Marijn Haverbeke) as part of the CodeMirror/Lezer ecosystem; this dependency is expected and stable for this package. | ai | |
| provenance | no-provenance | AI (provenance): Official CodeMirror package by Marijn Haverbeke; lack of provenance attestation is common and not a meaningful risk signal for this well-established author. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 6.0.2 | 2 / 1 | |
| 6.0.0 | 2 / 1 | |
| 0.20.0 | 2 / 1 | |
| 0.19.2 | 3 / 1 | |
| 0.19.0 | 3 / 1 | |
| 0.18.0 | 3 / 3 | |
| 0.17.1 | 4 / 3 | |
| 0.17.0 | 4 / 3 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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.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.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.