← Home

@webex/internal-plugin-encryption

npm Repository
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
semgrep semgrep:base64-decode AI (semgrep): Base64 decode is used for PEM-to-DER certificate parsing — standard cryptographic operation, not obfuscation. ai
phantom-deps phantom-dep:@webex/test-helper-file AI (phantom-deps): Test helper dependency in same org scope; phantom-dep false positive for monorepo test infrastructure. ai

Versions (showing 5 of 5)

Version Deps Published
3.12.0 18 / 13
3.11.0 18 / 13
3.10.0 18 / 13
3.9.0 18 / 13
3.8.1 18 / 13

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.