@empiricalrun/playwright-utils@0.66.1
Playwright utils for test code repos of our customers
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package sends content-bearing overlay and test telemetry to its own service when the related feature runs, with no telemetry disclosure found in the README. The behavior is suspicious rather than malicious because it uses the package's service and does not exfiltrate credentials to a foreign host.
Decision evidence
public snapshot- Telemetry is sent to /api/v1/telemetry/track when EMPIRICALRUN_API_KEY is set.
- The overlay.dismissed event includes overlay text and description, the failing locator, project and repository names, and test context.
- The overlay-dismissal flow collects that text and calls the telemetry function during feature execution.
- The API client defaults to https://api.empirical.run and permits a user-configured DASHBOARD_DOMAIN.
- The telemetry requires the package's Empirical API key and goes to its own service by default.
- The inspected manifest scripts are build, test, lint and development tasks; no install lifecycle hook was found.
- The flagged npx command runs Playwright's merge-reports command only from the reporter's local-testing path.
Source & flagged code
7 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.66.1.
See all versions of @empiricalrun/playwright-utils for other recorded verdicts.
- Review the evidence and your use of @empiricalrun/playwright-utils@0.66.1 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.