← Home

@webex/plugin-team-memberships

5
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.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@webex/plugin-rooms AI (phantom-deps): Monorepo pattern; same-org dependencies resolved at build/runtime. ai
phantom-deps phantom-dep:@webex/plugin-teams AI (phantom-deps): Monorepo pattern; same-org dependencies resolved at build/runtime. ai
phantom-deps phantom-dep:@webex/plugin-logger AI (phantom-deps): Monorepo pattern; same-org dependencies resolved at build/runtime. ai
npm-metadata no-description AI (npm-metadata): Empty description is common in monorepo packages; not a malware signal here. ai
phantom-deps phantom-dep:@webex/internal-plugin-device AI (phantom-deps): Same-org @webex/* monorepo package; phantom-dep heuristic is a stable false positive here. ai

Versions (showing 5 of 5)

Version Deps Published
3.12.0 2 / 12
3.11.0 2 / 12
3.10.0 2 / 12
3.9.0 2 / 12
3.8.1 5 / 12

v3.12.0

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.

v3.11.0

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.

v3.10.0

1 finding
LOW No provenance attestation provenance

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

v3.9.0

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.

v3.8.1

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.