@codemirror/lang-sql MIT 40 versions

@codemirror/lang-sql

npm Repository Homepage

SQL language support for the CodeMirror code editor

40

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

adrianheinemarijn

Keywords

editorcode

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@lezer/lr	AI (dependencies): @lezer/lr is a core Lezer parser runtime by the same author (Marijn Haverbeke); a legitimate and expected dependency for CodeMirror language packages.	ai	2026/04/21
dependencies	unvetted-dep:@lezer/common	AI (dependencies): @lezer/common is a core Lezer library by the same author; expected dependency for CodeMirror language packages.	ai	2026/04/21
dependencies	unvetted-dep:@lezer/highlight	AI (dependencies): @lezer/highlight is a core Lezer library by the same author; expected dependency for CodeMirror language packages.	ai	2026/04/21
dependencies	unvetted-dep:@codemirror/language	AI (dependencies): @codemirror/language is a core CodeMirror 6 package by the same author; expected dependency for a language extension.	ai	2026/04/21
dependencies	unvetted-dep:@codemirror/autocomplete	AI (dependencies): @codemirror/autocomplete is a core CodeMirror 6 package by the same author; expected dependency for SQL language support with autocomplete.	ai	2026/04/21
phantom-deps	phantom-dep:@lezer/common	AI (phantom-deps): @lezer/common being referenced only in config files is a benign packaging pattern for this CodeMirror ecosystem package; not a security concern.	ai	2026/04/21

Versions (showing 40 of 40)

Version	Deps	Published
6.10.0	6 / 1	2025-09-16
6.9.1	6 / 1	2025-07-28
6.9.0	6 / 1	2025-05-30
6.8.0	6 / 1	2024-10-01
6.7.1	6 / 1	2024-08-21
6.7.0	6 / 1	2024-06-24
6.6.5	6 / 1	2024-06-17
6.6.4	6 / 1	2024-05-04
6.6.3	6 / 1	2024-04-08
6.6.2	6 / 1	2024-03-23
6.6.1	6 / 1	2024-03-04
6.6.0	6 / 1	2024-02-29
6.5.5	6 / 1	2023-12-28
6.5.4	5 / 1	2023-08-10
6.5.3	5 / 1	2023-08-05
6.5.2	5 / 1	2023-06-23
6.5.1	5 / 1	2023-06-21
6.5.0	5 / 1	2023-05-16
6.4.1	5 / 1	2023-04-13
6.4.0	5 / 1	2023-01-23
6.3.3	5 / 1	2022-11-14
6.3.2	5 / 1	2022-10-24
6.3.1	5 / 1	2022-10-17
6.3.0	5 / 1	2022-08-23
6.2.0	5 / 1	2022-08-14
6.1.0	5 / 1	2022-08-05
6.0.0	5 / 1	2022-06-08
0.20.4	5 / 1	2022-05-30
0.20.3	5 / 1	2022-05-27
0.20.2	5 / 1	2022-05-24
0.20.1	5 / 1	2022-05-24
0.20.0	5 / 1	2022-04-20
0.19.4	5 / 1	2021-10-28
0.19.3	5 / 1	2021-08-21
0.19.2	5 / 1	2021-08-11
0.19.0	5 / 1	2021-08-11
0.18.0	5 / 7	2021-03-03
0.17.2	5 / 7	2021-02-01
0.17.1	5 / 7	2021-01-06
0.17.0	5 / 7	2020-12-29

v6.9.1

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.8.0

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.6.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.6.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.6.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.6.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.6.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.5.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.5.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.5.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.5.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.5.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.3.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.3.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.2.0

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.20.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.20.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.20.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.20.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.20.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.19.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.19.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.19.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.19.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.18.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.17.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.