← Home

browserstack-cypress-cli

npm Repository Homepage

BrowserStack Cypress CLI for Cypress integration with BrowserStack's remote devices.

12
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

browserstack-admin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): CLI tool legitimately uses child_process for spawning Cypress and git commands; stable false positive for this package. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require is used to load the user's own package.json; benign and stable for this CLI tool. ai
semgrep semgrep:base64-decode AI (semgrep): base64UrlDecode is a standard JWT/token utility; no evidence of payload hiding. ai
phantom-deps phantom-dep:mkdirp AI (phantom-deps): mkdirp is declared in dependencies and used transitively; phantom-dep heuristic false positive. ai

Versions (showing 12 of 12)

Version Deps Published
1.36.13 28 / 8
1.36.12 28 / 8
1.36.11 28 / 8
1.32.7 25 / 8
1.32.6 25 / 8
1.32.5 25 / 8
1.32.4 25 / 8
1.32.3 25 / 8
1.32.2 25 / 8
1.32.1 25 / 8
1.32.0 25 / 8
1.0.1 0 / 5

v1.36.13

1 finding
LOW No provenance attestation provenance

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

v1.36.12

1 finding
LOW No provenance attestation provenance

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

v1.36.11

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.

v1.32.7

1 finding
LOW No provenance attestation provenance

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

v1.32.6

1 finding
LOW No provenance attestation provenance

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

v1.32.5

1 finding
LOW No provenance attestation provenance

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

v1.32.4

1 finding
LOW No provenance attestation provenance

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

v1.32.3

1 finding
LOW No provenance attestation provenance

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

v1.32.2

1 finding
LOW No provenance attestation provenance

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

v1.32.1

1 finding
LOW No provenance attestation provenance

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

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

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