@empiricalrun/playwright-utils@0.58.5
Playwright utils for test code repos of our customers
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection found legitimate, opt-in Playwright utilities and reporting rather than install-time or covert attack behavior. Static findings reflect intended network, credential, child-process, and cached automation features.
Decision evidence
public snapshot- Webhook helpers explicitly send only caller-supplied token/query data using configured provider credentials.
- The optional reporter uploads Playwright attachments and test-result metadata when configured.
- Overlay tooling executes code from its local .empiricalrun cache during an explicitly enabled test fixture.
- package.json has no preinstall, install, or postinstall hook.
- Main import only re-exports utilities; no network or child-process action is invoked on import.
- Reporter upload is gated on configured run identifiers, storage backend, and credentials.
- No broad credential harvesting, foreign agent-config mutation, stealth persistence, or remote payload loading found.
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.5.
See all versions of @empiricalrun/playwright-utils for other recorded verdicts.
- Review the evidence and your use of @empiricalrun/playwright-utils@0.58.5 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.