@microsoft/teams.dev
<p> <a href="https://www.npmjs.com/package/@microsoft/teams.dev" target="_blank"> <img src="https://img.shields.io/npm/v/@microsoft/teams.dev/latest" /> </a> <a href="https://www.npmjs.com/package/@microsoft/teams.dev?activeTab=code" t
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/devtools-web/assets/index-WXyg8WWt.js | AI (source-diff): Vite-bundled React devtools UI; minification is expected for this asset. | ai | |
| source-diff | net-exec-file:dist/devtools-web/assets/index-WXyg8WWt.js | AI (source-diff): Network calls and dynamic code in a browser SPA bundle are normal; no dropper indicators in sample. | ai | |
| source-diff | obfuscated-file:dist/devtools-web/assets/index-DttdYIoC.js | AI (source-diff): Vite-bundled devtools web UI asset; minification is expected for this package's frontend component. | ai | |
| source-diff | net-exec-file:dist/devtools-web/assets/index-DttdYIoC.js | AI (source-diff): Browser SPA bundle; fetch calls and dynamic patterns are standard React/Vite output, not dropper behavior. | ai | |
| source-diff | net-exec-file:dist/devtools-web/assets/index-B4lvAsXI.js | AI (source-diff): Network calls and dynamic code are normal browser app patterns in this Vite bundle; no dropper behavior. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): axios is a declared runtime dependency; phantom-dep heuristic false positive for this package. | ai | |
| source-diff | obfuscated-file:dist/devtools-web/assets/index-B4lvAsXI.js | AI (source-diff): Standard Vite-minified React/Fluent UI bundle; not obfuscated malware. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.0.11 | 8 / 11 | |
| 2.0.10 | 8 / 11 | |
| 2.0.9 | 8 / 11 | |
| 2.0.8 | 8 / 11 | |
| 2.0.7 | 8 / 11 |
v2.0.11
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.9
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.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.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.