@microsoft/vscode-azext-webview
Common tools for web views in VS Code 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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/cjs/src/webview/TemplateGallery/TemplateGalleryView.js | AI (source-diff): Standard tsc-compiled React/JSX output from Microsoft's build pipeline; long lines are bundled component markup, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/esm/src/webview/TemplateGallery/TemplateGalleryView.js | AI (source-diff): Same as CJS counterpart — tsc-compiled React output with visible copyright headers and standard module boilerplate. | ai | |
| phantom-deps | phantom-dep:sass-loader | AI (phantom-deps): UI build tooling referenced in esbuild config, not a direct import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@vscode/codicons | AI (phantom-deps): Icon assets referenced in build config, not directly imported in source; expected pattern for VS Code extensions. | ai | |
| phantom-deps | phantom-dep:@fluentui/react-icons | AI (phantom-deps): Fluent UI icons likely re-exported or used indirectly; common pattern in VS Code webview packages. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.1.0 | 12 / 6 | |
| 1.0.2 | 10 / 6 | |
| 1.0.1 | 10 / 6 | |
| 1.0.0 | 10 / 6 |
v1.1.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.