@webex/internal-plugin-lyra
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:@webex/common | AI (dependencies): Same-org monorepo sibling; not an independent risk. | ai | |
| dependencies | unvetted-dep:@webex/webex-core | AI (dependencies): Same-org monorepo sibling; not an independent risk. | ai | |
| dependencies | unvetted-dep:@webex/internal-plugin-locus | AI (dependencies): Same-org monorepo sibling; not an independent risk. | ai | |
| dependencies | unvetted-dep:@webex/internal-plugin-feature | AI (dependencies): Same-org monorepo sibling; not an independent risk. | ai | |
| dependencies | unvetted-dep:@webex/internal-plugin-mercury | AI (dependencies): Same-org monorepo sibling; not an independent risk. | ai | |
| dependencies | unvetted-dep:@webex/internal-plugin-encryption | AI (dependencies): Same-org monorepo sibling; not an independent risk. | ai | |
| dependencies | unvetted-dep:@webex/internal-plugin-conversation | AI (dependencies): Same-org monorepo sibling; not an independent risk. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Declared in package.json; used transitively or in config — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:bowser | AI (phantom-deps): Declared in package.json; used transitively or in config — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@webex/internal-plugin-locus | AI (phantom-deps): Same-org sibling; phantom-dep heuristic unreliable for monorepo packages. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.12.0 | 9 / 15 | |
| 3.11.0 | 9 / 16 | |
| 3.10.0 | 9 / 16 | |
| 3.9.0 | 9 / 16 | |
| 3.8.1 | 9 / 16 |
v3.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.