@microsoft/omnichannel-chat-sdk
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:acs_webchat-chat-adapter | AI (dependencies): Microsoft/Azure-owned adapter package, consistent with SDK's ACS dependencies. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): First-party Azure Communication Services dependency, not a supply-chain risk. | ai | |
| dependencies | unvetted-dep:@azure/communication-common | AI (dependencies): First-party Azure SDK dependency expected for this Microsoft Omnichannel SDK. | ai | |
| dependencies | unvetted-dep:@microsoft/omnichannel-ic3core | AI (dependencies): First-party Microsoft Omnichannel dependency expected for this SDK. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() used for config property validation by key name — not obfuscation; stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@microsoft/botframework-webchat-adapter-azure-communication-chat | AI (dependencies): First-party Microsoft BotFramework dependency expected for this SDK. | ai | |
| dependencies | unvetted-dep:@microsoft/omnichannel-amsclient | AI (dependencies): First-party Microsoft Omnichannel dependency expected for this SDK. | ai | |
| dependencies | unvetted-dep:@azure/communication-chat | AI (dependencies): First-party Azure SDK dependency expected for this Microsoft Omnichannel SDK. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.11.8 | 6 / 10 | |
| 1.11.7 | 6 / 9 | |
| 1.11.0 | 6 / 9 | |
| 1.10.20 | 6 / 9 | |
| 1.10.10 | 6 / 9 | |
| 1.10.1 | 6 / 9 | |
| 1.10.0 | 5 / 9 | |
| 1.9.10 | 5 / 9 | |
| 1.9.9 | 5 / 9 | |
| 1.9.8 | 5 / 9 | |
| 1.9.7 | 5 / 8 | |
| 1.9.6 | 5 / 8 | |
| 1.9.5 | 5 / 8 | |
| 1.9.4 | 5 / 8 | |
| 1.9.3 | 5 / 8 | |
| 1.9.2 | 5 / 8 | |
| 1.9.1 | 5 / 8 | |
| 1.9.0 | 5 / 8 | |
| 1.8.3 | 5 / 8 | |
| 1.8.2 | 5 / 8 |
v1.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.