@empiricalrun/playwright-utils@0.62.0
Playwright utils for test code repos of our customers
AI Security Review
scanned 27d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or concrete attack behavior. The flagged webhook and subprocess code has explicit test utility behavior and no confirmed unrelated credential destination.
Decision evidence
public snapshot- package.json exposes the library through dist/index.js and lists development and test scripts, with no install lifecycle hook.
- The webhook API creates and queries webhook.site resources when its exported functions are called; it uses a caller-provided webhook.site key for that service.
- The API client defaults to api.empirical.run and allows the caller to configure its base URL.
- The local reporter runs Playwright's merge-reports command to produce local HTML and JSON reports.
- The upstream oracle runs npm tests against a supplied Playwright clone.
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.62.0.
See all versions of @empiricalrun/playwright-utils for other recorded verdicts.
- Review the evidence and your use of @empiricalrun/playwright-utils@0.62.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.