codemirror-graphql
GraphQL mode and helpers for CodeMirror.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Moved to GitHub Actions CI/CD publishing with SLSA provenance; legitimate for graphql/graphiql monorepo. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Mature stable package in graphiql monorepo; infrequent releases are normal. | ai | |
| phantom-deps | phantom-dep:@types/codemirror | AI (phantom-deps): Type-only dependency; not directly imported at runtime. | ai |
Versions (showing 100 of 100)
| Version | Deps | Published |
|---|---|---|
| 2.2.6 | 2 / 6 | |
| 2.2.5 | 2 / 6 | |
| 2.2.4 | 2 / 6 | |
| 2.2.3 | 2 / 6 | |
| 2.2.2 | 2 / 6 | |
| 2.2.1 | 2 / 6 | |
| 2.2.0 | 2 / 6 | |
| 2.1.1 | 2 / 6 | |
| 2.1.0 | 2 / 6 | |
| 2.0.13 | 2 / 6 | |
| 2.0.12 | 2 / 6 | |
| 2.0.11 | 2 / 6 | |
| 2.0.10 | 2 / 6 | |
| 2.0.9 | 1 / 6 | |
| 2.0.8 | 1 / 6 | |
| 2.0.7 | 1 / 6 | |
| 2.0.6 | 1 / 6 | |
| 2.0.5 | 1 / 6 | |
| 2.0.4 | 1 / 6 | |
| 2.0.3 | 1 / 6 | |
| 2.0.2 | 1 / 6 | |
| 2.0.1 | 1 / 6 | |
| 2.0.0 | 1 / 6 | |
| 1.3.2 | 1 / 7 | |
| 1.3.1 | 1 / 7 | |
| 1.3.0 | 1 / 7 | |
| 1.2.17 | 2 / 6 | |
| 1.2.16 | 2 / 6 | |
| 1.2.15 | 2 / 6 | |
| 1.2.14 | 2 / 6 | |
| 1.2.13 | 2 / 6 | |
| 1.2.12 | 2 / 6 | |
| 1.2.11 | 2 / 6 | |
| 1.2.10 | 2 / 6 | |
| 1.2.9 | 2 / 6 | |
| 1.2.8 | 2 / 6 | |
| 1.2.7 | 2 / 6 | |
| 1.2.6 | 2 / 6 | |
| 1.2.5 | 2 / 6 | |
| 1.2.4 | 2 / 6 | |
| 1.2.3 | 2 / 6 | |
| 1.2.2 | 2 / 6 | |
| 1.2.1 | 2 / 6 | |
| 1.2.0 | 2 / 6 | |
| 1.1.0 | 2 / 6 | |
| 1.0.3 | 2 / 6 | |
| 1.0.2 | 2 / 6 | |
| 1.0.1 | 2 / 6 | |
| 1.0.0 | 2 / 6 | |
| 0.15.2 | 2 / 10 | |
| 0.15.1 | 2 / 10 | |
| 0.15.0 | 2 / 10 | |
| 0.14.0 | 2 / 10 | |
| 0.13.1 | 2 / 10 | |
| 0.13.0 | 2 / 10 | |
| 0.12.4 | 2 / 10 | |
| 0.12.3 | 2 / 10 | |
| 0.12.2 | 2 / 10 | |
| 0.12.1 | 2 / 10 | |
| 0.12.0 | 2 / 10 | |
| 0.11.6 | 2 / 9 | |
| 0.11.5 | 2 / 9 | |
| 0.11.4 | 2 / 9 | |
| 0.11.3 | 2 / 8 | |
| 0.11.2 | 2 / 7 | |
| 0.11.1 | 2 / 7 | |
| 0.9.0 | 2 / 7 | |
| 0.8.3 | 2 / 35 | |
| 0.8.2 | 2 / 35 | |
| 0.7.1 | 2 / 35 | |
| 0.6.12 | 2 / 35 | |
| 0.6.11 | 2 / 35 | |
| 0.6.10 | 2 / 35 | |
| 0.6.9 | 2 / 35 | |
| 0.6.8 | 2 / 35 | |
| 0.6.7 | 2 / 35 | |
| 0.6.6 | 2 / 34 | |
| 0.6.5 | 2 / 34 | |
| 0.6.4 | 2 / 34 | |
| 0.6.3 | 0 / 34 | |
| 0.6.2 | 0 / 34 | |
| 0.6.1 | 0 / 34 | |
| 0.6.0 | 0 / 34 | |
| 0.5.9 | 0 / 34 | |
| 0.5.8 | 0 / 34 | |
| 0.5.7 | 0 / 12 | |
| 0.5.6 | 0 / 12 | |
| 0.5.5 | 0 / 12 | |
| 0.5.4 | 0 / 12 | |
| 0.5.3 | 0 / 12 | |
| 0.5.2 | 0 / 12 | |
| 0.5.1 | 0 / 12 | |
| 0.5.0 | 0 / 12 | |
| 0.3.1 | 0 / 12 | |
| 0.3.0 | 0 / 12 | |
| 0.2.2 | 0 / 12 | |
| 0.2.1 | 0 / 12 | |
| 0.2.0 | 0 / 12 | |
| 0.1.1 | 0 / 12 | |
| 0.1.0 | 0 / 12 |
v2.2.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.5
2 findingsThis version was published by a different npm account than previous versions on 2026-05-11. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.