@empiricalrun/playwright-utils@0.60.0
Playwright utils for test code repos of our customers
AI Security Review
scanned 28d ago · by lpm-firewall-aiSource inspection found no lifecycle hooks or concrete malicious behavior. The webhook credential use is directed to webhook.site for its token API, while dynamic execution is limited to a caller-invoked cache helper.
Decision evidence
public snapshot- package.json points to the package’s JavaScript entrypoint and declares its exports.
- The local report helper invokes Playwright’s merge-reports command with explicit arguments and the current working directory.
- The webhook helper reads an explicitly configured webhook.site API key and sends it to webhook.site’s token endpoint for token creation.
- The upstream oracle imports child-process support as part of a runner test harness.
- The overlay cache runs stored code against a supplied Playwright page when its exported execution function is called.
- No lifecycle scripts are declared in package.json.
- Inspected webhook code handles webhook.site and inbox token creation and queries; it does not show environment or credential harvesting to an unrelated destination.
- The dynamic execution is confined to the overlay cache helper, which reads a package-specific cache and executes against a caller-provided page.
Source & flagged code
9 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.60.0.
See all versions of @empiricalrun/playwright-utils for other recorded verdicts.
- Review the evidence and your use of @empiricalrun/playwright-utils@0.60.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.