@codemirror/autocomplete
Autocompletion 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/tooltip | AI (dependencies): @codemirror/tooltip is a sibling package in the CodeMirror ecosystem published by the same trusted author (marijn); this dependency relationship is stable and expected across versions. | ai | |
| dependencies | unvetted-dep:@lezer/common | AI (dependencies): @lezer/common is a first-party dependency from the same CodeMirror/Lezer ecosystem by Marijn Haverbeke; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@codemirror/view | AI (dependencies): @codemirror/view is a core CodeMirror package by the same author; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@codemirror/state | AI (dependencies): @codemirror/state is a core CodeMirror package by the same author; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@codemirror/language | AI (dependencies): @codemirror/language is a core CodeMirror package by the same author; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): CodeMirror packages are published without Sigstore provenance; publisher identity and track record are well-established. Stable false positive for this package. | ai |
Versions (showing 51 of 88)
| Version | Deps | Published |
|---|---|---|
| 6.20.2 | 4 / 1 | |
| 6.20.1 | 4 / 1 | |
| 6.20.0 | 4 / 1 | |
| 6.19.1 | 4 / 1 | |
| 6.19.0 | 4 / 1 | |
| 6.18.7 | 4 / 1 | |
| 6.18.6 | 4 / 1 | |
| 6.18.5 | 4 / 1 | |
| 6.18.4 | 4 / 1 | |
| 6.18.3 | 4 / 1 | |
| 6.18.2 | 4 / 1 | |
| 6.18.1 | 4 / 1 | |
| 6.18.0 | 4 / 1 | |
| 6.17.0 | 4 / 1 | |
| 6.16.3 | 4 / 1 | |
| 6.16.2 | 4 / 1 | |
| 6.16.1 | 4 / 1 | |
| 6.16.0 | 4 / 1 | |
| 6.15.0 | 4 / 1 | |
| 6.14.0 | 4 / 1 | |
| 6.13.0 | 4 / 1 | |
| 6.12.0 | 4 / 1 | |
| 6.11.1 | 4 / 1 | |
| 6.11.0 | 4 / 1 | |
| 6.10.2 | 4 / 1 | |
| 6.10.1 | 4 / 1 | |
| 6.10.0 | 4 / 1 | |
| 6.9.2 | 4 / 1 | |
| 6.9.1 | 4 / 1 | |
| 6.9.0 | 4 / 1 | |
| 6.8.1 | 4 / 1 | |
| 6.8.0 | 4 / 1 | |
| 6.7.1 | 4 / 1 | |
| 6.7.0 | 4 / 1 | |
| 6.6.1 | 4 / 1 | |
| 6.6.0 | 4 / 1 | |
| 6.5.1 | 4 / 1 | |
| 6.5.0 | 4 / 1 | |
| 6.4.2 | 4 / 1 | |
| 6.4.1 | 4 / 1 | |
| 6.4.0 | 4 / 1 | |
| 6.3.4 | 4 / 1 | |
| 6.3.3 | 4 / 1 | |
| 6.3.2 | 4 / 1 | |
| 6.3.1 | 4 / 1 | |
| 6.3.0 | 4 / 1 | |
| 6.2.0 | 4 / 1 | |
| 6.1.1 | 4 / 1 | |
| 6.1.0 | 4 / 1 | |
| 6.0.4 | 4 / 1 | |
| 6.0.3 | 4 / 1 |
v6.20.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.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.
v6.19.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.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.18.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.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.
v6.16.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.16.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.16.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.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
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.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.1
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.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. 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.