@empiricalrun/playwright-utils@0.58.0
Playwright utils for test code repos of our customers
AI Security Review
scanned 3mo ago · by lpm-firewall-aiScanner claims conflate configured authentication headers and explicit test-reporting integrations with credential exfiltration. Source contains no install-time execution or unconsented collection, execution, persistence, or control-surface modification.
Decision evidence
public snapshot- dist/webhook.js uses configured API keys for webhook provider requests.
- dist/reporter/uploader.js can upload explicitly configured test artifacts.
- dist/telemetry.js posts telemetry only when EMPIRICAL_TELEMETRY_API_KEY is set.
- package.json has no preinstall, install, or postinstall hook.
- dist/index.js only defines exports; importing it does not invoke network or shell actions.
- dist/webhook.js sends keys only as authorization to its selected webhook/API service.
- dist/reporter/local-test.js runs a fixed Playwright report-merge command when called.
- No source evidence of environment harvesting, remote code loading, persistence, or agent-config mutation.
Source & flagged code
6 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.0.
See all versions of @empiricalrun/playwright-utils for other recorded verdicts.
- Review the evidence and your use of @empiricalrun/playwright-utils@0.58.0 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.