← Home

@webex/media-helpers

Package that provides helper functions for media related activities.

15
Versions
Cisco's General Terms (https://www.cisco.com/site/us/en/about/legal/contract-experience/index.html)
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, so a manually published version cannot be tied back to a reviewed commit.

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
license uncommon-license:Cisco EULA https://www.cisco.com/c/en/us/products/end-user-license-agreement.html AI (license): Cisco proprietary license; expected for Webex packages. ai
dependencies unvetted-dep:@webex/ts-events AI (dependencies): Internal @webex scoped dependency from the same Webex SDK monorepo; stable false positive for this package. ai
dependencies unvetted-dep:@webex/web-media-effects AI (dependencies): Internal @webex scoped dependency from the same Webex SDK monorepo; stable false positive for this package. ai
provenance no-provenance AI (provenance): Cisco/Webex SDK org does not use Sigstore provenance; consistent across all versions. ai

Versions (showing 15 of 15)

Version Deps Published
3.12.0 3 / 12
3.11.0 3 / 12
3.10.0 3 / 12
3.9.0 3 / 10
3.8.1 3 / 10
3.8.0 3 / 10
3.7.0 3 / 10
3.6.0 3 / 10
3.5.0 3 / 10
3.4.0 3 / 10
3.3.1 3 / 10
3.3.0 3 / 10
3.2.0 3 / 10
3.1.0 3 / 10
3.0.1 3 / 9

v3.8.0

1 finding
INFO No provenance attestation provenance

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

v3.7.0

1 finding
INFO No provenance attestation provenance

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

v3.6.0

1 finding
INFO No provenance attestation provenance

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

v3.5.0

1 finding
INFO No provenance attestation provenance

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

v3.4.0

1 finding
INFO No provenance attestation provenance

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

v3.3.1

1 finding
INFO No provenance attestation provenance

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

v3.3.0

1 finding
INFO No provenance attestation provenance

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

v3.2.0

1 finding
INFO No provenance attestation provenance

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

v3.1.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.0.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.