vscode-json-languageservice
Language service for JSON
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): Microsoft/vscode-bot publish environment change; gitHead presence is not security-critical for this trusted package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from vscode-bot to microsoft1es is a legitimate Microsoft internal bot account rotation; both are established Microsoft publishing accounts. | ai | |
| provenance | no-provenance | AI (provenance): Microsoft's vscode ecosystem packages have historically published without Sigstore provenance; not a security concern for this publisher. | ai |
Versions (showing 100 of 133)
| Version | Deps | Published |
|---|---|---|
| 5.7.2 | 5 / 9 | |
| 5.7.1 | 5 / 9 | |
| 5.7.0 | 5 / 9 | |
| 5.6.4 | 5 / 9 | |
| 5.6.3 | 5 / 9 | |
| 5.6.2 | 5 / 9 | |
| 5.6.1 | 5 / 9 | |
| 5.6.0 | 5 / 9 | |
| 5.5.0 | 5 / 9 | |
| 5.4.4 | 5 / 9 | |
| 5.4.3 | 5 / 9 | |
| 5.4.2 | 5 / 9 | |
| 5.4.1 | 5 / 9 | |
| 5.4.0 | 5 / 9 | |
| 5.3.11 | 5 / 9 | |
| 5.3.10 | 5 / 9 | |
| 5.3.9 | 5 / 9 | |
| 5.3.7 | 5 / 9 | |
| 5.3.6 | 5 / 9 | |
| 5.3.5 | 5 / 9 | |
| 5.3.4 | 5 / 9 | |
| 5.3.3 | 5 / 9 | |
| 5.3.2 | 5 / 9 | |
| 5.3.1 | 5 / 9 | |
| 5.3.0 | 5 / 9 | |
| 5.2.0 | 5 / 9 | |
| 5.1.4 | 5 / 9 | |
| 5.1.3 | 5 / 9 | |
| 5.1.2 | 5 / 9 | |
| 5.1.1 | 5 / 9 | |
| 5.1.0 | 5 / 8 | |
| 5.0.0 | 5 / 8 | |
| 4.2.1 | 5 / 8 | |
| 4.2.0 | 5 / 8 | |
| 4.1.10 | 5 / 8 | |
| 4.1.9 | 5 / 8 | |
| 4.1.8 | 5 / 8 | |
| 4.1.7 | 5 / 8 | |
| 4.1.6 | 5 / 8 | |
| 4.1.5 | 6 / 9 | |
| 4.1.4 | 6 / 9 | |
| 4.1.3 | 6 / 9 | |
| 4.1.2 | 6 / 9 | |
| 4.1.0 | 6 / 9 | |
| 4.0.2 | 5 / 8 | |
| 4.0.1 | 5 / 8 | |
| 4.0.0 | 5 / 8 | |
| 3.11.0 | 5 / 8 | |
| 3.10.0 | 5 / 9 | |
| 3.9.1 | 5 / 9 | |
| 3.9.0 | 5 / 9 | |
| 3.8.5 | 5 / 9 | |
| 3.8.4 | 5 / 9 | |
| 3.8.3 | 5 / 9 | |
| 3.8.2 | 5 / 9 | |
| 3.8.1 | 5 / 9 | |
| 3.8.0 | 5 / 9 | |
| 3.7.0 | 5 / 9 | |
| 3.6.0 | 5 / 9 | |
| 3.5.2 | 5 / 6 | |
| 3.5.1 | 5 / 6 | |
| 3.4.12 | 5 / 6 | |
| 3.4.11 | 5 / 6 | |
| 3.4.10 | 5 / 6 | |
| 3.4.9 | 5 / 6 | |
| 3.4.8 | 5 / 6 | |
| 3.4.7 | 5 / 6 | |
| 3.4.6 | 5 / 6 | |
| 3.4.5 | 5 / 6 | |
| 3.4.4 | 5 / 6 | |
| 3.4.3 | 4 / 6 | |
| 3.4.1 | 4 / 6 | |
| 3.4.0 | 4 / 6 | |
| 3.3.5 | 4 / 6 | |
| 3.3.4 | 4 / 6 | |
| 3.3.3 | 4 / 6 | |
| 3.3.2 | 4 / 6 | |
| 3.3.1 | 4 / 6 | |
| 3.3.0 | 4 / 6 | |
| 3.2.1 | 4 / 6 | |
| 3.2.0 | 4 / 6 | |
| 3.1.7 | 4 / 6 | |
| 3.1.6 | 4 / 6 | |
| 3.1.5 | 4 / 6 | |
| 3.1.4 | 4 / 6 | |
| 3.1.3 | 4 / 6 | |
| 3.1.2 | 4 / 6 | |
| 3.1.0 | 4 / 6 | |
| 3.0.13 | 4 / 6 | |
| 3.0.12 | 4 / 6 | |
| 3.0.11 | 4 / 6 | |
| 3.0.10 | 4 / 5 | |
| 3.0.8 | 4 / 5 | |
| 3.0.7 | 4 / 5 | |
| 3.0.6 | 4 / 5 | |
| 3.0.5 | 4 / 5 | |
| 3.0.4 | 4 / 5 | |
| 3.0.3 | 4 / 5 | |
| 3.0.2 | 4 / 5 | |
| 3.0.1 | 4 / 5 |
v5.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.4
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.4.3
2 findingsThis version was published by a different npm account than previous versions on 2025-01-27. 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.4.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.4.1
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.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.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.2.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.1.4
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.1.3
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.1.2
3 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.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-11-10. This could indicate a legitimate maintainer transition or an account compromise.
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
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.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.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
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.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.