@vscode/debugprotocol
Npm module with declarations for the Visual Studio Code debug protocol
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Consistent with Microsoft's bot publish env; no source-integrity concern for this package. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Legitimate move to Microsoft's vscode-bot publishing account; stable across versions. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Microsoft org maintainer consolidation to vscode-bot; benign. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Corresponds to same Microsoft bot consolidation. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.68.0 | 0 / 1 | |
| 1.67.0 | 0 / 1 | |
| 1.66.0 | 0 / 1 | |
| 1.65.0 | 0 / 1 | |
| 1.64.0 | 0 / 1 | |
| 1.63.0 | 0 / 1 | |
| 1.61.0 | 0 / 1 | |
| 1.59.0 | 0 / 1 | |
| 1.58.0 | 0 / 0 | |
| 1.57.0 | 0 / 0 | |
| 1.56.1 | 0 / 0 | |
| 1.56.0 | 0 / 0 | |
| 1.55.1 | 0 / 0 | |
| 1.55.0 | 0 / 0 | |
| 1.54.0 | 0 / 1 | |
| 1.53.0 | 0 / 1 | |
| 1.51.0 | 0 / 1 |
v1.67.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.66.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.0
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.
This version was published by a different npm account (vscode-bot) than the most recent previously approved version (connor.peet) on 2024-02-27. It has since remained available on npm for 875 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.64.0
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.
This version was published by a different npm account (vscode-bot) than the most recent previously approved version (connor.peet) on 2023-10-27. It has since remained available on npm for 997 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.63.0
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.
This version was published by a different npm account (vscode-bot) than the most recent previously approved version (connor.peet) on 2023-08-31. It has since remained available on npm for 1054 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.61.0
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.
This version was published by a different npm account (vscode-bot) than the most recent previously approved version (connor.peet) on 2023-06-05. It has since remained available on npm for 1141 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.59.0
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.
This version was published by a different npm account (vscode-bot) than the most recent previously approved version (connor.peet) on 2023-01-29. It has since remained available on npm for 1269 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.56.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.56.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.55.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (connor.peet) than the most recent previously approved version (aweinand) on 2022-03-23, but connor.peet is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.55.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (connor.peet) than the most recent previously approved version (aweinand) on 2022-03-23, but connor.peet is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.53.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (connor.peet) than the most recent previously approved version (aweinand) on 2022-02-03, but connor.peet is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.