← Home

@webex/test-users

Cisco Webex Test Users

15
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, 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
provenance no-provenance AI (provenance): Established package; provenance absence is common and not a disqualifier for mature packages. ai
dependencies unvetted-dep:node-random-name AI (dependencies): node-random-name is a benign name-generation utility; appropriate for a test-users package across all versions. ai
phantom-deps phantom-dep:@webex/test-helper-mocha AI (phantom-deps): Package is legitimately listed as a runtime dependency in package.json; phantom-dep fires because it's also a devDependency. ai

Versions (showing 15 of 15)

Version Deps Published
3.12.0 6 / 13
3.11.0 6 / 13
3.10.0 6 / 13
3.9.0 6 / 13
3.8.1 6 / 13
3.8.0 6 / 13
3.7.0 6 / 13
3.6.0 6 / 13
3.5.0 6 / 13
3.4.0 6 / 13
3.3.1 6 / 13
3.3.0 6 / 13
3.2.0 6 / 13
3.1.0 6 / 13
3.0.0 6 / 13

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