vscode-html-languageservice
Language service for HTML
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
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 publishes Microsoft VS Code packages; missing gitHead reflects CI tooling change, not a security concern for this trusted publisher. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from vscode-bot to microsoft1es is an internal Microsoft publisher rotation; both are Microsoft service accounts. | ai | |
| provenance | no-provenance | AI (provenance): Informational only; Microsoft packages in this ecosystem commonly lack Sigstore provenance. | ai |
Versions (showing 51 of 80)
| Version | Deps | Published |
|---|---|---|
| 5.6.2 | 4 / 10 | |
| 5.6.1 | 4 / 10 | |
| 5.6.0 | 4 / 10 | |
| 5.5.2 | 4 / 10 | |
| 5.5.1 | 4 / 10 | |
| 5.5.0 | 4 / 10 | |
| 5.4.0 | 4 / 10 | |
| 5.3.3 | 4 / 10 | |
| 5.3.2 | 4 / 10 | |
| 5.3.1 | 4 / 10 | |
| 5.3.0 | 4 / 10 | |
| 5.2.0 | 4 / 10 | |
| 5.1.2 | 4 / 10 | |
| 5.1.1 | 4 / 10 | |
| 5.1.0 | 4 / 10 | |
| 5.0.7 | 4 / 10 | |
| 5.0.6 | 4 / 10 | |
| 5.0.5 | 4 / 10 | |
| 5.0.4 | 4 / 10 | |
| 5.0.3 | 4 / 10 | |
| 5.0.2 | 4 / 10 | |
| 5.0.1 | 4 / 10 | |
| 5.0.0 | 4 / 10 | |
| 4.2.5 | 4 / 10 | |
| 4.2.4 | 4 / 10 | |
| 4.2.2 | 4 / 10 | |
| 4.2.1 | 4 / 10 | |
| 4.2.0 | 4 / 10 | |
| 4.1.1 | 4 / 10 | |
| 4.1.0 | 4 / 10 | |
| 4.0.8 | 4 / 10 | |
| 4.0.7 | 4 / 10 | |
| 4.0.6 | 4 / 10 | |
| 4.0.5 | 4 / 10 | |
| 4.0.4 | 4 / 10 | |
| 4.0.3 | 4 / 10 | |
| 4.0.2 | 4 / 10 | |
| 4.0.1 | 4 / 10 | |
| 4.0.0 | 4 / 10 | |
| 3.2.0 | 4 / 10 | |
| 3.1.5 | 4 / 10 | |
| 3.1.4 | 4 / 10 | |
| 3.1.3 | 4 / 10 | |
| 3.1.2 | 4 / 10 | |
| 3.1.1 | 4 / 10 | |
| 3.1.0 | 4 / 10 | |
| 3.0.3 | 3 / 10 | |
| 3.0.2 | 3 / 10 | |
| 3.0.1 | 3 / 10 | |
| 3.0.0 | 3 / 10 | |
| 2.1.12 | 3 / 10 |
v5.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
2 findingsThis version was published by a different npm account than previous versions on 2025-03-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] 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.
v5.0.7
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] 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.
v5.0.6
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] 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.
v5.0.3
3 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] 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.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-11-25. This could indicate a legitimate maintainer transition or an account compromise.
v5.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.