vscode-uri
The URI implementation that is used by VS Code and its extensions
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): Maintainer rotation within Microsoft's VS Code team. New maintainers are known MS employees/bots. Publisher vscode-bot has strong track record (782 approved, 0 rejected). | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers are former MS employees rotated off npm access as part of org cleanup; not suspicious in context. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are established Microsoft/VS Code team members and the official vscode-bot publishing account. | ai | |
| source-diff | obfuscated-file:lib/esm/index.mjs | AI (source-diff): Webpack-bundled ESM output of URI/path utility code; accompanied by source map. Standard build artifact for this package. | ai | |
| provenance | publisher-changed | AI (provenance): microsoft1es is a known Microsoft org account (3383 approved packages). Transition from vscode-bot is a routine org-level change. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Mature stable utility library; long gaps between releases are normal and expected. | ai | |
| provenance | missing-githead | AI (provenance): Consequence of Microsoft's updated publish pipeline; no security implication for this package. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 0 / 9 | |
| 3.0.8 | 0 / 9 | |
| 3.0.7 | 0 / 9 | |
| 3.0.6 | 0 / 9 | |
| 3.0.5 | 0 / 9 | |
| 3.0.4 | 0 / 9 | |
| 3.0.3 | 0 / 9 | |
| 3.0.2 | 0 / 9 | |
| 3.0.1 | 0 / 9 | |
| 3.0.0 | 0 / 9 | |
| 2.1.2 | 0 / 1 | |
| 2.1.1 | 0 / 1 | |
| 2.1.0 | 0 / 1 | |
| 2.0.3 | 0 / 1 | |
| 2.0.2 | 0 / 1 | |
| 2.0.1 | 0 / 1 | |
| 2.0.0 | 0 / 1 | |
| 1.0.8 | 0 / 1 | |
| 1.0.7 | 0 / 1 | |
| 1.0.6 | 0 / 1 | |
| 1.0.5 | 0 / 1 | |
| 1.0.3 | 0 / 1 | |
| 1.0.2 | 0 / 1 | |
| 1.0.1 | 0 / 1 | |
| 1.0.0 | 0 / 2 | |
| 0.0.7 | 0 / 2 | |
| 0.0.6 | 0 / 2 | |
| 0.0.5 | 0 / 2 | |
| 0.0.4 | 0 / 2 | |
| 0.0.3 | 0 / 2 | |
| 0.0.2 | 0 / 2 | |
| 0.0.1 | 1 / 0 |
v3.1.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: microsoft1es.
This version was published by a different npm account than previous versions on 2025-02-04. 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.
v3.0.8
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
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.
v3.0.7
4 findingsAll previous maintainers (jrieken, egamma, aeschli) were replaced by new maintainers (alexandrudima, kaimaetzel, sbatten, microsoft1es, lszomoru, vscode-bot). This is a strong signal of a potential package hijack and requires careful review.
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-12-13. This could indicate a legitimate maintainer transition or an account compromise.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
2 findingsPackage 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-09-15. This could indicate a legitimate maintainer transition or an account compromise.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.