@empiricalrun/playwright-utils@0.63.0
Playwright utils for test code repos of our customers
AI Security Review
scanned 21d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook. The reported process launch is a local report merge, and the webhook API-key use belongs to caller-invoked provider testing; no malicious attack surface remains.
Decision evidence
public snapshot- package.json declares the package entrypoints and scripts, with no install lifecycle hook.
- The local report helper runs Playwright's merge-reports command in the supplied working directory.
- The incremental reporter calls that helper only during finalization when local testing is detected.
- Webhook helpers create or query the selected provider using caller-supplied options, URL, and content.
- The direct webhook provider path sends its API key to webhook.site's token API.
- The webhook matcher queries using its caller-supplied webhook URL and content.
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.63.0.
See all versions of @empiricalrun/playwright-utils for other recorded verdicts.
- Review the evidence and your use of @empiricalrun/playwright-utils@0.63.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.