@vscode/extension-telemetry
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@microsoft/1ds-core-js | AI (phantom-deps): 1DS SDK dependency used in build/config context; stable false positive for this telemetry package. | ai | |
| phantom-deps | phantom-dep:@microsoft/1ds-post-js | AI (phantom-deps): 1DS SDK dependency used in build/config context; stable false positive for this telemetry package. | ai | |
| phantom-deps | phantom-dep:@microsoft/applicationinsights-core-js | AI (phantom-deps): AppInsights core used in build/config context; stable false positive for this telemetry package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.5.2 | 5 / 10 | |
| 1.5.1 | 3 / 11 | |
| 1.5.0 | 3 / 11 | |
| 1.4.0 | 3 / 11 | |
| 1.3.0 | 3 / 11 | |
| 1.2.0 | 3 / 11 | |
| 1.1.0 | 3 / 11 | |
| 1.0.0 | 3 / 11 |
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.