← Home

@webex/http-core

Core HTTP library for the Cisco Webex

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/webex-core AI (phantom-deps): Same-org package; used as peer/integration dep, not directly imported in this library. ai
phantom-deps phantom-dep:@webex/internal-plugin-device AI (phantom-deps): Same-org package; declared for integration testing context, not a direct import. ai
phantom-deps phantom-dep:@webex/test-helper-test-users AI (phantom-deps): Test-helper package listed in both deps and devDeps; not a direct import in library code. ai
dependencies unvetted-dep:request AI (dependencies): request@^2.88.0 is a well-known, widely-used HTTP library; stable false positive for this package. ai
provenance no-provenance AI (provenance): Large Cisco Webex monorepo; provenance attestation not yet adopted across the project, consistent across all versions. ai

Versions (showing 5 of 5)

Version Deps Published
3.12.0 10 / 14
3.11.0 10 / 14
3.10.0 10 / 14
3.9.0 10 / 14
3.8.1 13 / 14

v3.10.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.9.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.8.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.