@vscode/web-custom-data
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): vscode-bot migration across Microsoft org packages, longstanding and stable. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Expected fallout of bot-based publishing migration, not a takeover. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Long-stable publisher change (1358d), inconsistent with compromise. | ai | |
| provenance | missing-githead | AI (provenance): Metadata-only regression on a long-trusted MS package; no behavioral change. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.6.3 | 0 / 5 | |
| 0.6.2 | 0 / 5 | |
| 0.6.1 | 0 / 4 | |
| 0.6.0 | 0 / 4 | |
| 0.5.2 | 0 / 3 | |
| 0.5.1 | 0 / 3 | |
| 0.5.0 | 0 / 3 | |
| 0.4.13 | 0 / 2 | |
| 0.4.12 | 0 / 2 | |
| 0.4.11 | 0 / 2 | |
| 0.4.9 | 0 / 2 | |
| 0.4.8 | 0 / 2 | |
| 0.4.7 | 0 / 2 | |
| 0.4.6 | 0 / 3 | |
| 0.4.5 | 0 / 3 | |
| 0.4.4 | 0 / 3 | |
| 0.4.3 | 0 / 3 | |
| 0.4.2 | 0 / 3 | |
| 0.4.1 | 0 / 3 | |
| 0.4.0 | 0 / 3 | |
| 0.3.10 | 0 / 3 | |
| 0.3.9 | 0 / 3 | |
| 0.3.8 | 0 / 3 | |
| 0.3.7 | 0 / 3 | |
| 0.3.6 | 0 / 3 |
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.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 (microsoft1es) than the most recent previously approved version (vscode-bot) on 2025-03-24, but microsoft1es 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.
v0.4.13
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 (microsoft1es) than the most recent previously approved version (vscode-bot) on 2024-12-02, but microsoft1es 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.
v0.4.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.9
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 (aeschli) on 2024-01-22. It has since remained available on npm for 913 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.
v0.4.8
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 (aeschli) on 2023-09-07. It has since remained available on npm for 1050 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.
v0.4.7
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 (aeschli) on 2023-08-28. It has since remained available on npm for 1060 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.
v0.4.6
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 (aeschli) on 2023-03-27. It has since remained available on npm for 1214 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.
v0.4.5
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 (aeschli) on 2023-01-23. It has since remained available on npm for 1277 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.
v0.4.4
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 (aeschli) on 2022-11-03. It has since remained available on npm for 1358 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.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.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: aeschli.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.