@codemirror/text
Document data structure 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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:next | AI (typosquat): @codemirror/text is a legitimate CodeMirror sub-package by Marijn Haverbeke; the Levenshtein match to 'next' on the short suffix 'text' is a stable false positive for this scoped package. | ai | |
| typosquat | typosquat.levenshtein:nuxt | AI (typosquat): @codemirror/text is a legitimate CodeMirror sub-package; the Levenshtein match to 'nuxt' is a stable false positive for this scoped package. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): @codemirror/text is a legitimate CodeMirror sub-package; the Levenshtein match to 'jest' is a stable false positive for this scoped package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.19.6 | 0 / 1 | |
| 0.19.5 | 0 / 1 | |
| 0.19.4 | 0 / 1 | |
| 0.19.3 | 0 / 1 | |
| 0.19.2 | 0 / 1 | |
| 0.19.1 | 0 / 1 | |
| 0.19.0 | 0 / 1 | |
| 0.18.1 | 0 / 1 | |
| 0.18.0 | 0 / 6 | |
| 0.17.2 | 0 / 6 | |
| 0.17.1 | 0 / 6 | |
| 0.17.0 | 0 / 6 |
v0.19.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
2 findingsPackage name '@codemirror/text' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.