@validate.qa/runner@1.0.104
validate local test runner - execute Playwright tests on your machine, connected to validate.qa cloud.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe inspected code fits a local Playwright runner: its credential-related logic checks browser-state token expiry, while sign-in lease traffic uses the configured runner server. The only lifecycle script is prepublishOnly, which runs the build; the scanner’s critical leads were not confirmed as malicious behavior.
Decision evidence
public snapshot- The manifest describes a local Playwright test runner and exposes dist/cli.js as its command-line entry point.
- The package’s prepublishOnly script runs the build; no install hook is declared.
- The run-write guard inspects browser storage tokens to determine expiry, rather than sending token values.
- The sandbox helper is invoked with a timeout and a restricted environment containing PATH.
- The sign-in lease request uses the configured server URL and authorization header for the runner’s sign-in lease endpoint.
Source & flagged code
15 flaggedPackage source references dynamic require/import behavior.
dist/discovery-mcp-server.jsView on unpkg · L15Source appears to collect browser login credentials for exfiltration.
dist/run-write-guard.jsView on unpkg · L144Findings
Affected versions and remediation
This report applies to @validate.qa/runner@1.0.104.
See all versions of @validate.qa/runner for other recorded verdicts.
- Review the evidence and your use of @validate.qa/runner@1.0.104 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.