@azure/communication-common
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 |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is used to decode an HMAC secret key for SHA-256 signing — standard crypto utility, not a payload concern. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a well-known implicit TypeScript runtime dependency; stable false positive for Azure SDK packages. | ai | |
| phantom-deps | phantom-dep:events | AI (phantom-deps): events polyfill referenced in browser config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@azure/core-tracing | AI (phantom-deps): Framework-scoped Azure tracing package loaded by convention; stable false positive. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.4.2 | 9 / 18 | |
| 2.4.1 | 9 / 14 | |
| 2.4.0 | 9 / 14 | |
| 2.3.1 | 8 / 31 |
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.