@codemirror/lint
Linting 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:@codemirror/panel | AI (dependencies): @codemirror/panel is a sibling package in the CodeMirror ecosystem published by the same author (marijn); this dependency is expected and benign for all versions of this package. | ai | |
| typosquat | typosquat.levenshtein:eslint | AI (typosquat): @codemirror/lint is a legitimate scoped package in the CodeMirror ecosystem; Levenshtein match to 'eslint' is a false positive with no impersonation intent. | ai | |
| typosquat | typosquat.levenshtein:pino | AI (typosquat): @codemirror/lint is a legitimate scoped package in the CodeMirror ecosystem; Levenshtein match to 'pino' is a false positive with no impersonation intent. | ai | |
| provenance | no-provenance | AI (provenance): Established publisher (marijn/Marijn Haverbeke) with long npm history; lack of Sigstore provenance is common and not a risk signal for this package. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 6.9.6 | 3 / 1 | |
| 6.9.5 | 3 / 1 | |
| 6.9.4 | 3 / 1 | |
| 6.9.3 | 3 / 1 | |
| 6.9.2 | 3 / 1 | |
| 6.9.1 | 3 / 1 | |
| 6.9.0 | 3 / 1 | |
| 6.8.5 | 3 / 1 | |
| 6.8.4 | 3 / 1 | |
| 6.8.3 | 3 / 1 | |
| 6.8.2 | 3 / 1 | |
| 6.8.1 | 3 / 1 | |
| 6.8.0 | 3 / 1 | |
| 6.7.1 | 3 / 1 | |
| 6.7.0 | 3 / 1 | |
| 6.6.0 | 3 / 1 | |
| 6.5.0 | 3 / 1 | |
| 6.4.2 | 3 / 1 | |
| 6.4.1 | 3 / 1 | |
| 6.4.0 | 3 / 1 | |
| 6.3.0 | 3 / 1 | |
| 6.2.2 | 3 / 1 | |
| 6.2.1 | 3 / 1 | |
| 6.2.0 | 3 / 1 | |
| 6.1.1 | 3 / 1 | |
| 6.1.0 | 3 / 1 | |
| 6.0.0 | 3 / 1 | |
| 0.20.3 | 3 / 1 | |
| 0.20.2 | 3 / 1 | |
| 0.20.1 | 3 / 1 | |
| 0.20.0 | 3 / 1 | |
| 0.19.5 | 7 / 1 | |
| 0.19.4 | 7 / 1 | |
| 0.19.3 | 7 / 1 | |
| 0.19.2 | 5 / 1 | |
| 0.19.1 | 5 / 1 | |
| 0.18.5 | 5 / 1 | |
| 0.18.4 | 5 / 1 | |
| 0.18.3 | 5 / 1 | |
| 0.18.2 | 5 / 1 | |
| 0.17.1 | 5 / 3 |
v6.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.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.9.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.9.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.
v6.9.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.
v6.9.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.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.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.7.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.
v6.7.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.6.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.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.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.
v6.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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.
v6.1.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.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.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.5
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.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.
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.18.5
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.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.
v0.18.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.
v0.18.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.