@empiricalrun/playwright-utils@0.58.3
Playwright utils for test code repos of our customers
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection shows a Playwright utility package with user-invoked, credential-gated provider and reporting integrations. The static credential-exfiltration and runtime-install labels are not supported as malicious behavior.
Decision evidence
public snapshot- Manifest exposes library/reporting entrypoints and contains no lifecycle hook.
- Webhook calls occur only inside exported async helpers and require a configured provider key.
- API client sends its configured Empirical API key only as an Authorization header to its configured base URL.
- Report upload is disabled unless several explicit project, run, backend, and storage-credential environment variables are set.
- The child-process finding runs a fixed Playwright report-merge command in local-test flow.
- No install-time execution, hidden downloader, dynamic code execution, or persistence mechanism found.
- No evidence that arbitrary environment variables, auth-state files, or credentials are harvested and sent to an attacker-controlled endpoint.
- Scanner's webhook credential-exfiltration label conflates explicit authenticated provider API use with credential theft.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/reporter/local-test.jsView on unpkg · L6Package source invokes a package manager install command at runtime.
dist/reporter/local-test.jsView on unpkg · L13Findings
Affected versions and remediation
This report applies to @empiricalrun/playwright-utils@0.58.3.
See all versions of @empiricalrun/playwright-utils for other recorded verdicts.
- Review the evidence and your use of @empiricalrun/playwright-utils@0.58.3 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.