← Home

@microsoft/omnichannel-chat-sdk

npm Repository Homepage
4
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

microsoft1esmicrosoft-oss-releasesdeeptijoshi123shengchensaponceraidhagecoryeuromaparnadubeycaniemanggilaberbghcoreelopezanaya

Keywords

SDKchatlivechatsupportbotheadlesscustomer

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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:@azure/communication-chat AI (dependencies): First-party Azure SDK dependency expected for this Microsoft Omnichannel SDK. 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
dependencies unvetted-dep:@microsoft/omnichannel-amsclient AI (dependencies): First-party Microsoft Omnichannel dependency expected for this SDK. ai
dependencies unvetted-dep:@microsoft/botframework-webchat-adapter-azure-communication-chat AI (dependencies): First-party Microsoft BotFramework dependency expected for this SDK. ai

Versions (showing 4 of 4)

Version Deps Published
1.11.8 6 / 10
1.11.7 6 / 9
1.11.0 6 / 9
1.10.20 6 / 9

v1.11.8

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.

v1.11.7

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.

v1.11.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.10.20

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.