vscode-css-languageservice

Language service for CSS, LESS and SCSS

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

microsoft1esmicrosoft-oss-releasesalexandrudimajoaomoreno.mskaimaetzelsbattenlszomoruvscode-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): vscode-bot publish pipeline change explains missing gitHead; consistent with Microsoft's shift to automated CI/CD publishing. Not a malware indicator for this well-established Microsoft package.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Established Microsoft package published by trusted vscode-bot; lack of Sigstore attestation is a best-practice gap, not a security risk for this well-known package.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): New maintainers are Microsoft/VS Code team members and the vscode-bot automation account — consistent with normal team evolution for this Microsoft-owned package.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): Removed maintainers (egamma, aeschli, dbaeumer) are former Microsoft employees; removal reflects normal team transitions, not a hostile takeover.	ai	2026/04/24
publish-pattern	new-deps-added	AI (publish-pattern): @vscode/l10n is a Microsoft-owned package replacing vscode-nls as the localization library — a documented migration within the VS Code ecosystem.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): microsoft1es is a known Microsoft publishing account with strong track record; transition from vscode-bot is consistent with Microsoft's internal account reorganization, not a compromise.	ai	2026/04/24

Versions (showing 51 of 105)

Hide prereleases View all versions

Version	Deps	Published
6.3.10	4 / 11	2026-02-23
6.3.9	4 / 11	2025-12-01
6.3.8	4 / 11	2025-09-29
6.3.7	4 / 11	2025-06-30
6.3.6	4 / 11	2025-06-02
6.3.5	4 / 11	2025-04-25
6.3.4	4 / 11	2025-04-03
6.3.3	4 / 11	2025-03-24
6.3.2	4 / 11	2024-12-02
6.3.1	4 / 11	2024-08-26
6.3.0	4 / 11	2024-06-24
6.2.14	4 / 11	2024-04-22
6.2.13	4 / 11	2024-03-22
6.2.12	4 / 11	2024-01-22
6.2.11	4 / 11	2023-11-27
6.2.10	4 / 11	2023-10-09
6.2.9	4 / 11	2023-09-25
6.2.8	4 / 11	2023-09-25
6.2.7	4 / 11	2023-08-28
6.2.6	4 / 11	2023-05-26
6.2.5	4 / 11	2023-04-24
6.2.4	4 / 11	2023-02-20
6.2.3	4 / 11	2023-01-25
6.2.2	4 / 11	2023-01-23
6.2.1	4 / 11	2022-11-22
6.1.1	4 / 11	2022-09-15
6.1.0	4 / 11	2022-09-05
6.0.1	4 / 10	2022-05-18
6.0.0	4 / 10	2022-05-18
5.4.2	4 / 10	2022-04-25
5.4.1	4 / 10	2022-04-01
5.3.0	4 / 10	2022-03-23
5.2.0	4 / 10	2022-03-18
5.1.13	4 / 9	2022-02-10
5.1.12	4 / 9	2022-01-24
5.1.11	4 / 9	2022-01-24
5.1.10	4 / 9	2022-01-24
5.1.9	4 / 9	2021-11-29
5.1.8	4 / 9	2021-10-25
5.1.7	4 / 9	2021-09-28
5.1.6	4 / 9	2021-09-27
5.1.5	4 / 9	2021-09-09
5.1.4	4 / 9	2021-06-28
5.1.3	4 / 9	2021-05-31
5.1.2	4 / 9	2021-05-31
5.1.1	4 / 9	2021-04-24
5.1.0	4 / 9	2021-02-05
5.0.3	4 / 9	2021-01-25
5.0.2	4 / 9	2020-12-18
5.0.1	4 / 9	2020-12-18
5.0.0	4 / 9	2020-12-14

v6.3.10

1 finding

LOW No provenance attestation provenance

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

v6.3.9

1 finding

LOW No provenance attestation provenance

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

v6.3.8

1 finding

LOW No provenance attestation provenance

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

v6.3.7

1 finding

LOW No provenance attestation provenance

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

v6.3.6

1 finding

LOW No provenance attestation provenance

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

v6.3.5

1 finding

LOW No provenance attestation provenance

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

v6.3.4

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

2 findings

HIGH Publisher changed: vscode-bot → microsoft1es (on 2024-12-02) provenance

This version was published by a different npm account than previous versions on 2024-12-02. This could indicate a legitimate maintainer transition or an account compromise.

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. Consider requesting the maintainer enable provenance via CI/CD.

v6.3.0

1 finding

LOW No provenance attestation provenance

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

v6.2.14

1 finding

LOW No provenance attestation provenance

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

v6.2.13

1 finding

INFO No provenance attestation provenance

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

v6.2.12

1 finding

INFO No provenance attestation provenance

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

v6.2.11

1 finding

INFO No provenance attestation provenance

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

v6.2.10

1 finding

INFO No provenance attestation provenance

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

v6.2.9

1 finding

INFO No provenance attestation provenance

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

v6.2.8

1 finding

LOW No provenance attestation provenance

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

v6.2.7

1 finding

LOW No provenance attestation provenance

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

v6.2.6

1 finding

LOW No provenance attestation provenance

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

v6.2.5

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vscode-bot.

LOW No provenance attestation provenance

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

v6.2.4

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vscode-bot.

INFO No provenance attestation provenance

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

v6.2.3

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vscode-bot.

INFO No provenance attestation provenance

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

v6.2.2

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vscode-bot.

INFO No provenance attestation provenance

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

INFO Publisher changed: aeschli → vscode-bot (on 2023-01-23) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2023-01-23. This could indicate a legitimate maintainer transition or an account compromise.

v6.2.1

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vscode-bot.

LOW No provenance attestation provenance

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

INFO Publisher changed: aeschli → vscode-bot (on 2022-11-22) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2022-11-22. This could indicate a legitimate maintainer transition or an account compromise.

v6.1.1

1 finding

LOW No provenance attestation provenance

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

v6.1.0

1 finding

INFO No provenance attestation provenance

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

v6.0.1

1 finding

INFO No provenance attestation provenance

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

v6.0.0

1 finding

INFO No provenance attestation provenance

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

v5.4.2

1 finding

INFO No provenance attestation provenance

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

v5.4.1

1 finding

INFO No provenance attestation provenance

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

v5.3.0

1 finding

INFO No provenance attestation provenance

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

v5.2.0

1 finding

INFO No provenance attestation provenance

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

v5.1.13

1 finding

INFO No provenance attestation provenance

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

v5.1.12

1 finding

INFO No provenance attestation provenance

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

v5.1.11

1 finding

INFO No provenance attestation provenance

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

v5.1.10

1 finding

INFO No provenance attestation provenance

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

v5.1.9

1 finding

INFO No provenance attestation provenance

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

v5.1.8

1 finding

INFO No provenance attestation provenance

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

v5.1.7

1 finding

INFO No provenance attestation provenance

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

v5.1.6

1 finding

INFO No provenance attestation provenance

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

v5.1.5

1 finding

INFO No provenance attestation provenance

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

v5.1.4

1 finding

INFO No provenance attestation provenance

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

v5.1.3

1 finding

INFO No provenance attestation provenance

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

v5.1.2

1 finding

INFO No provenance attestation provenance

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

v5.1.1

1 finding

INFO No provenance attestation provenance

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

v5.1.0

1 finding

INFO No provenance attestation provenance

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

v5.0.3

1 finding

INFO No provenance attestation provenance

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

v5.0.2

1 finding

INFO No provenance attestation provenance

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

v5.0.1

1 finding

INFO No provenance attestation provenance

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

v5.0.0

1 finding

INFO No provenance attestation provenance

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