@azure/communication-chat
2
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
azure-sdkmicrosoft1es
Keywords
azurecloudAzurecommunicationchat
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Size increase reflects tshy multi-dialect build output (esm/commonjs/browser/react-native), not injected code. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Same root cause: multi-dialect dist output added in this version. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Microsoft Azure SDK; dormancy reflects SDK release cadence, not account takeover risk. | ai | |
| phantom-deps | phantom-dep:@azure/core-auth | AI (phantom-deps): Framework-scoped Azure package loaded by convention; stable false positive for this SDK. | ai | |
| phantom-deps | phantom-dep:@azure/abort-controller | AI (phantom-deps): Framework-scoped Azure package loaded by convention; stable false positive for this SDK. | ai |
v1.6.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.