@microsoft/vscode-azext-utils
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): @microsoft/vscode-processutils is a first-party Microsoft package; low risk for this org-owned package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): microsoft-oss-releases is a Microsoft OSS release automation account; addition is expected for this org's packages. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): microsoft1es is a well-established Microsoft publisher; gap in publishing is consistent with normal release cadence changes, not account takeover. | ai | |
| dependencies | unvetted-dep:vscode-tas-client | AI (dependencies): VS Code experimentation client; long-standing dep in this package's ecosystem. | ai | |
| dependencies | unvetted-dep:@microsoft/vscode-azureresources-api | AI (dependencies): First-party Microsoft Azure VS Code API package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@microsoft/vscode-processutils | AI (dependencies): First-party Microsoft package added as a runtime dep; consistent with package purpose. | ai | |
| dependencies | unvetted-dep:@vscode/extension-telemetry | AI (dependencies): Official VS Code telemetry package from Microsoft; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft package; provenance absence is consistent across all 129 versions and not a risk indicator here. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.1.0 | 7 / 8 | |
| 4.0.8 | 7 / 8 | |
| 4.0.7 | 7 / 8 | |
| 4.0.6 | 7 / 8 | |
| 4.0.5 | 6 / 7 | |
| 4.0.4 | 6 / 6 | |
| 4.0.3 | 7 / 6 | |
| 4.0.2 | 7 / 15 | |
| 4.0.1 | 7 / 15 | |
| 4.0.0 | 7 / 15 |
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.