@microsoft/omnichannel-chat-components
Microsoft Omnichannel Chat Components
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@fluentui/react | AI (dependencies): Microsoft's own Fluent UI library; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:jest-transform-stub | AI (dependencies): Test utility stub; low-risk, widely used in test configs. | ai | |
| dependencies | unvetted-dep:botframework-webchat | AI (dependencies): Microsoft Bot Framework package; expected dependency for this omnichannel chat component. | ai | |
| provenance | no-provenance | AI (provenance): Official Microsoft package; provenance absence is common and not a risk signal here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Microsoft package; sparse README/keywords are cosmetic issues, not risk signals. | ai | |
| phantom-deps | phantom-dep:styled-components | AI (phantom-deps): Styling dependency used indirectly; stable false positive for this UI component package. | ai | |
| phantom-deps | phantom-dep:botframework-webchat | AI (phantom-deps): Legitimate Microsoft dependency; phantom detection is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:jest-transform-stub | AI (phantom-deps): Dev/test config reference only; not a runtime concern for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.1.19 | 7 / 48 | |
| 1.1.18 | 7 / 46 | |
| 1.1.17 | 7 / 48 | |
| 1.1.15 | 7 / 46 | |
| 1.1.13 | 7 / 46 | |
| 1.1.11 | 7 / 44 | |
| 1.1.10 | 7 / 44 | |
| 1.1.9 | 7 / 44 |
v1.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.