@webex/plugin-teams
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@webex/test-helper-test-users | AI (phantom-deps): Test helper in devDependencies; used in test suite. | ai | |
| phantom-deps | phantom-dep:@webex/plugin-rooms | AI (phantom-deps): Monorepo plugin dependency; imported indirectly via plugin system. | ai | |
| phantom-deps | phantom-dep:@webex/plugin-logger | AI (phantom-deps): Monorepo plugin dependency; imported indirectly via plugin system. | ai | |
| phantom-deps | phantom-dep:@webex/test-helper-chai | AI (phantom-deps): Test helper in devDependencies; used in test suite. | ai | |
| phantom-deps | phantom-dep:@webex/plugin-memberships | AI (phantom-deps): Monorepo plugin dependency; imported indirectly via plugin system. | ai | |
| provenance | no-provenance | AI (provenance): Established Webex SDK package; lack of provenance is consistent across all versions. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is a declared runtime dep; phantom-dep heuristic misfires here. | ai | |
| phantom-deps | phantom-dep:@webex/internal-plugin-device | AI (phantom-deps): Same-org dep declared in dependencies; phantom-dep heuristic misfires for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Webex SDK monorepo packages consistently omit descriptions; stable false positive. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.12.0 | 3 / 12 | |
| 3.11.0 | 3 / 12 | |
| 3.10.0 | 3 / 12 | |
| 3.9.0 | 3 / 12 | |
| 3.8.1 | 8 / 12 |
v3.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 finding[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[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.