@wdio/browserstack-service@9.39.5
WebdriverIO service for better Browserstack integration
AI Security Review
scanned 24d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or concrete attack chain. The flagged subprocess and network behavior is consistent with the BrowserStack service’s CLI, Git orchestration, and flag-triggered reporting functions.
Decision evidence
public snapshot- package.json exposes the BrowserStack service and a separate cleanup entrypoint; its listed scripts contain no install lifecycle hook.
- Cleanup sends funnel data only when the corresponding command-line flag and data are present; its request goes to the package’s instrumentation endpoint.
- The spawned SDK CLI is obtained through the service’s setup path, and the other flagged process calls run fixed Git commands for test orchestration.
- No concrete malicious behavior was identified in the inspected runtime paths.
- Importing the cleanup entrypoint starts cleanup handling, which can send supplied funnel data or upload logs when command-line flags request those actions.
- The service spawns a CLI process with the current environment, and test orchestration runs Git commands and reads their output.
Source & flagged code
5 flaggedSource combines command execution, command-output handling, and outbound requests; review data flow before blocking.
build/index.jsView on unpkg · L19Findings
Affected versions and remediation
This report applies to @wdio/browserstack-service@9.39.5.
See all versions of @wdio/browserstack-service for other recorded verdicts.
- Review the evidence and your use of @wdio/browserstack-service@9.39.5 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.