@microsoft/teams.client
<p> <a href="https://www.npmjs.com/package/@microsoft/teams.client" target="_blank"> <img src="https://img.shields.io/npm/v/@microsoft/teams.client/latest" /> </a> <a href="https://www.npmjs.com/package/@microsoft/teams.client?activeTa
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): Microsoft org publish infra change; not a security signal for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): microsoft-oss-releases is a known Microsoft automation account. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Declared dep referenced in config; stable false positive. | ai | |
| phantom-deps | phantom-dep:@microsoft/teams.api | AI (phantom-deps): Same-org sibling dep; likely re-exported rather than directly imported. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.0.12 | 4 / 7 | |
| 2.0.11 | 4 / 7 | |
| 2.0.10 | 4 / 7 | |
| 2.0.9 | 4 / 7 | |
| 2.0.8 | 5 / 7 | |
| 2.0.7 | 5 / 7 | |
| 2.0.6 | 5 / 7 | |
| 2.0.5 | 2 / 7 | |
| 2.0.4 | 2 / 7 | |
| 2.0.3 | 2 / 7 | |
| 2.0.2 | 2 / 7 | |
| 2.0.1 | 2 / 7 | |
| 2.0.0 | 2 / 7 |
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
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (microsoft1es) than the most recent previously approved version (aamirjawaid) on 2026-03-25, but microsoft1es is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.