@uiw/codemirror-extensions-langs
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
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; stable for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Inlined official @codemirror/lang-* deps previously bundled via @codemirror/language-data. | ai | |
| dependencies | unvetted-dep:codemirror-lang-mermaid | AI (dependencies): Community CodeMirror 6 language extension for Mermaid diagrams; expected dependency for a language loader package. | ai | |
| dependencies | unvetted-dep:@nextjournal/lang-clojure | AI (dependencies): Nextjournal's CodeMirror 6 Clojure language extension; legitimate third-party language plugin. | ai | |
| dependencies | unvetted-dep:@replit/codemirror-lang-nix | AI (dependencies): Replit's CodeMirror 6 Nix language extension; published by a well-known company. | ai | |
| provenance | no-provenance | AI (provenance): Established package from a known publisher with 131 approved packages and 8+ year history; lack of provenance attestation is not a meaningful risk signal here. | ai | |
| dependencies | unvetted-dep:@replit/codemirror-lang-svelte | AI (dependencies): Replit's CodeMirror 6 Svelte language extension; published by a well-known company. | ai | |
| dependencies | unvetted-dep:@replit/codemirror-lang-solidity | AI (dependencies): Replit's CodeMirror 6 Solidity language extension; published by a well-known company. | ai | |
| dependencies | unvetted-dep:@replit/codemirror-lang-csharp | AI (dependencies): Replit's CodeMirror 6 C# language extension; published by a well-known company. | ai | |
| dependencies | unvetted-dep:@codemirror/lang-lezer | AI (dependencies): Official @codemirror scope language extension; legitimate dependency for a CodeMirror language loader package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 4.25.10 | 26 / 4 | |
| 4.25.9 | 26 / 4 | |
| 4.25.8 | 26 / 4 | |
| 4.25.7 | 26 / 4 | |
| 4.25.6 | 26 / 4 | |
| 4.25.5 | 6 / 3 | |
| 4.25.4 | 6 / 3 | |
| 4.25.3 | 6 / 3 | |
| 4.25.2 | 6 / 3 | |
| 4.25.1 | 6 / 3 | |
| 4.25.0 | 6 / 3 | |
| 4.24.2 | 27 / 0 | |
| 4.24.1 | 27 / 0 | |
| 4.24.0 | 27 / 0 | |
| 4.23.14 | 27 / 0 | |
| 4.23.13 | 27 / 0 | |
| 4.23.12 | 27 / 0 | |
| 4.23.11 | 27 / 0 | |
| 4.21.12 | 26 / 0 |
v4.25.10
2 findingsThis version was published by a different npm account than previous versions on 2026-05-21. 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.
v4.25.9
2 findingsThis version was published by a different npm account than previous versions on 2026-03-25. 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.
v4.25.8
2 findingsThis version was published by a different npm account than previous versions on 2026-03-08. 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.
v4.25.7
2 findingsThis version was published by a different npm account than previous versions on 2026-03-02. 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.
v4.25.6
2 findingsThis version was published by a different npm account than previous versions on 2026-03-02. 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.
v4.25.5
2 findingsThis version was published by a different npm account than previous versions on 2026-02-24. 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.
v4.25.4
2 findingsThis version was published by a different npm account than previous versions on 2025-12-12. 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.
v4.25.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.24.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.23.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.23.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.23.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.21.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.