@webex/internal-plugin-conversation
3
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
npm.tropowebex-jenkinsarun3528adamweekstaymoork2webex-components-publisherwebex-web-clientwebex-web-client-gen
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:node-scr | AI (dependencies): node-scr is a known Cisco/Webex SDK cryptographic dependency; its use here is expected and consistent across the monorepo. | ai | |
| dependencies | unvetted-dep:@webex/webex-core | AI (dependencies): Sibling package in the same monorepo/release train; not an independent risk. | ai | |
| dependencies | unvetted-dep:@webex/helper-image | AI (dependencies): Sibling package in the same monorepo/release train; not an independent risk. | ai | |
| dependencies | unvetted-dep:@webex/internal-plugin-user | AI (dependencies): Sibling package in the same monorepo/release train; not an independent risk. | ai | |
| dependencies | unvetted-dep:@webex/common | AI (dependencies): Sibling package in the same monorepo/release train; not an independent risk. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Empty description is a known pattern in this monorepo; not a malware indicator. | ai | |
| provenance | no-provenance | AI (provenance): Large established SDK; lack of Sigstore provenance is common and not a risk signal here. | ai | |
| dependencies | unvetted-dep:@webex/internal-plugin-encryption | AI (dependencies): Sibling package in the same monorepo/release train; not an independent risk. | ai |
v3.11.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.1
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.