@chat-adapter/teams
Supply chain provenance
Status for the latest visible version.
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 to GitHub Actions publisher with SLSA attestation is expected for Vercel CI/CD automation; stable pattern for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): haydenbleasel is a known Vercel engineer; addition is consistent with legitimate team expansion on the vercel/chat monorepo project. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @azure/identity and @microsoft/microsoft-graph-client are canonical Microsoft SDKs expected for a Teams adapter; their addition is contextually appropriate and not suspicious. | ai | |
| dependencies | unvetted-dep:@microsoft/microsoft-graph-client | AI (dependencies): @microsoft/microsoft-graph-client is Microsoft's official Graph API SDK — a well-known, widely-used library appropriate for a Teams adapter. Not a supply chain risk. | ai | |
| provenance | no-provenance | AI (provenance): Provenance absence is common (~88% of npm packages lack it) and is not a meaningful risk signal for this well-established publisher and package. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 4.30.0 | 6 / 5 | |
| 4.29.0 | 6 / 5 | |
| 4.28.1 | 6 / 5 | |
| 4.27.0 | 6 / 5 | |
| 4.26.0 | 6 / 5 | |
| 4.25.0 | 6 / 5 | |
| 4.24.0 | 6 / 5 | |
| 4.23.0 | 5 / 5 | |
| 4.22.0 | 5 / 5 | |
| 4.21.0 | 5 / 5 | |
| 4.20.2 | 5 / 5 | |
| 4.20.1 | 5 / 5 | |
| 4.20.0 | 5 / 5 | |
| 4.19.0 | 5 / 5 | |
| 4.18.0 | 5 / 5 | |
| 4.17.0 | 5 / 5 | |
| 4.16.1 | 4 / 5 | |
| 4.16.0 | 4 / 5 | |
| 4.15.0 | 4 / 5 | |
| 4.14.0 | 5 / 4 | |
| 4.13.4 | 5 / 4 | |
| 4.13.3 | 5 / 4 | |
| 4.13.2 | 5 / 4 | |
| 4.13.1 | 5 / 4 | |
| 4.13.0 | 5 / 4 | |
| 4.12.0 | 5 / 4 | |
| 4.11.0 | 5 / 4 | |
| 4.10.1 | 5 / 4 | |
| 4.10.0 | 5 / 4 | |
| 4.9.1 | 5 / 4 | |
| 4.9.0 | 5 / 4 | |
| 4.8.0 | 5 / 4 | |
| 4.7.2 | 5 / 4 | |
| 4.7.1 | 5 / 4 | |
| 4.7.0 | 5 / 4 | |
| 4.6.0 | 5 / 4 | |
| 4.5.0 | 5 / 4 | |
| 4.4.1 | 5 / 4 | |
| 4.4.0 | 5 / 4 | |
| 4.3.0 | 5 / 4 | |
| 4.2.0 | 4 / 4 | |
| 4.1.0 | 4 / 4 | |
| 4.0.2 | 2 / 4 | |
| 4.0.1 | 2 / 4 | |
| 4.0.0 | 2 / 4 |
v4.30.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.29.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.28.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.27.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-30. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.