@validate.qa/runner@1.0.109
validate local test runner - execute Playwright tests on your machine, connected to validate.qa cloud.
AI Security Review
scanned 9h ago · by lpm-firewall-aiThe manifest identifies a local Playwright runner and declares no install-time hook. The flagged dynamic-code and credential patterns are consistent with test validation and provider-specific AI configuration; no attack behavior was identified.
Decision evidence
public snapshot- The manifest describes a local Playwright test runner connected to the validate.qa cloud.
- The only lifecycle script is prepublishOnly, which runs the build; no install hook is declared.
- Provider API keys are mapped to their corresponding providers, consistent with the runner’s AI features.
- The write guard rejects tests that use eval or new Function to access protected guard handles.
- The runner uses dynamic function construction to check generated test code, which may trigger remote-code-execution heuristics.
- The package runs local tests and uses configured provider credentials, so it has normal process and network capabilities.
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.109.
See all versions of @validate.qa/runner for other recorded verdicts.
- Review the evidence and your use of @validate.qa/runner@1.0.109 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.