vscode-jsonrpc
A json rpc implementation over streams
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 | publisher-changed | AI (provenance): Publisher changed from individual (dbaeumer) to Microsoft's vscode-bot org account; legitimate organizational transition for all vscode-* packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (microsoft1es, lszomoru, vscode-bot) are Microsoft organizational accounts replacing individual devs. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers were individual MS employees; replaced by org-level accounts as part of standard MS publishing consolidation. | ai | |
| provenance | missing-githead | AI (provenance): vscode-jsonrpc is a Microsoft package published by vscode-bot; missing gitHead reflects CI tooling changes, not compromise. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft package; lack of Sigstore provenance is common and not a risk signal for this publisher. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 8.2.1 | 0 / 2 | |
| 8.2.0 | 0 / 2 | |
| 8.1.0 | 0 / 2 | |
| 8.0.2 | 0 / 2 | |
| 8.0.1 | 0 / 2 | |
| 8.0.0 | 0 / 2 | |
| 6.0.0 | 0 / 2 | |
| 5.0.1 | 0 / 0 | |
| 5.0.0 | 0 / 0 | |
| 4.0.0 | 0 / 0 | |
| 3.6.2 | 0 / 0 | |
| 3.6.1 | 0 / 0 | |
| 3.6.0 | 0 / 0 | |
| 3.5.0 | 0 / 0 | |
| 3.4.1 | 0 / 0 | |
| 3.4.0 | 0 / 0 | |
| 3.3.1 | 0 / 4 | |
| 3.3.0 | 0 / 4 | |
| 3.2.0 | 0 / 4 | |
| 3.1.0 | 0 / 4 | |
| 3.0.4 | 0 / 4 | |
| 3.0.3 | 0 / 4 | |
| 2.4.0 | 0 / 2 | |
| 2.3.1 | 0 / 2 | |
| 2.3.0 | 0 / 2 | |
| 2.2.0 | 0 / 2 | |
| 2.1.1 | 0 / 2 | |
| 2.1.0 | 0 / 2 | |
| 2.0.0 | 0 / 2 | |
| 1.2.0 | 0 / 2 | |
| 1.0.1 | 0 / 2 | |
| 0.10.1 | 0 / 2 | |
| 0.10.0 | 0 / 2 | |
| 9.0.0-next.11 | 0 / 2 | |
| 9.0.0-next.10 | 0 / 2 |
v8.2.1
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
3 findingsThis version was published by a different npm account than previous versions on 2023-02-14. This could indicate a legitimate maintainer transition or an account compromise.
[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.
v8.0.2
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: dbaeumer.
v8.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.