@microsoft/teams.mcp
<p> <a href="https://www.npmjs.com/package/@microsoft/teams.mcp" target="_blank"> <img src="https://img.shields.io/npm/v/@microsoft/teams.mcp/latest" /> </a> <a href="https://www.npmjs.com/package/@microsoft/teams.mcp?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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Deprecated package from trusted Microsoft publisher; missing gitHead is low risk given clean diff and no other indicators. | ai | |
| provenance | no-provenance | AI (provenance): Microsoft-published package; provenance gap is a process concern, not a security signal for this publisher. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is a declared runtime dep used via json-schema-to-zod; phantom-dep heuristic misfires here. | ai | |
| source-diff | obfuscated-file:dist/json-schema-to-zod.js | AI (source-diff): Readable compiled TS implementing json-schema-to-zod inline; long lines from minified test data, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/json-schema-to-zod.spec.js | AI (source-diff): Test spec file with long assertion lines; clearly readable, no malicious content. | ai | |
| source-diff | obfuscated-file:dist/plugin.spec.js | AI (source-diff): Test spec file; long lines from chained test assertions, not obfuscation. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.0.12 | 3 / 8 | |
| 2.0.11 | 3 / 8 | |
| 2.0.10 | 3 / 8 | |
| 2.0.9 | 3 / 8 | |
| 2.0.8 | 4 / 8 | |
| 2.0.7 | 4 / 8 | |
| 2.0.6 | 4 / 8 | |
| 2.0.5 | 2 / 8 | |
| 2.0.4 | 2 / 8 | |
| 2.0.3 | 2 / 8 | |
| 2.0.2 | 2 / 8 | |
| 2.0.1 | 2 / 8 | |
| 2.0.0 | 2 / 8 |
v2.0.12
2 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
2 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.
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
4 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.
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.
v2.0.8
1 findingPackage 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.
v2.0.6
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 2026-03-25. 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.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.