@microsoft/teams.ai
<p> <a href="https://www.npmjs.com/package/@microsoft/teams.ai" target="_blank"> <img src="https://img.shields.io/npm/v/@microsoft/teams.ai/latest" /> </a> <a href="https://www.npmjs.com/package/@microsoft/teams.ai?activeTab=code" targ
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 | publisher-changed | AI (provenance): Transition from aamirjawaid to microsoft1es is an internal Microsoft publisher consolidation; both are Microsoft-affiliated accounts. | ai | |
| provenance | missing-githead | AI (provenance): Likely a CI/CD pipeline change within Microsoft; no malicious signal given the trusted publisher context. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): microsoft-oss-releases is a Microsoft OSS automation account; addition is consistent with internal tooling changes. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @microsoft/teams.common is a first-party Microsoft package in the same monorepo at the same version; not a supply-chain risk. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.0.12 | 1 / 8 | |
| 2.0.11 | 1 / 8 | |
| 2.0.10 | 1 / 8 | |
| 2.0.9 | 1 / 8 | |
| 2.0.8 | 1 / 8 | |
| 2.0.7 | 1 / 8 | |
| 2.0.6 | 1 / 8 | |
| 2.0.5 | 0 / 8 | |
| 2.0.4 | 0 / 8 | |
| 2.0.3 | 0 / 8 | |
| 2.0.2 | 0 / 8 | |
| 2.0.1 | 0 / 8 | |
| 2.0.0 | 0 / 8 |
v2.0.12
1 findingPackage 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
1 findingPackage 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.