@empiricalrun/playwright-utils@0.62.1
Playwright utils for test code repos of our customers
AI Security Review
scanned 25d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and inspected flagged code shows package-aligned, caller-triggered webhook and report operations. Scanner indicators do not establish credential exfiltration or malicious behavior.
Decision evidence
public snapshot- The manifest exposes the library through dist/index.js and defines development/build scripts, with no install lifecycle hook.
- Webhook creation is an exported, caller-invoked API; it defaults to webhook.site and uses a supplied webhook-site API key only for a request to that service.
- The local report helper runs Playwright's merge-reports command with the caller-provided output directory and working directory.
- The upstream oracle file is a test harness for Playwright reporter behavior, not an install-time entrypoint.
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.1.
See all versions of @empiricalrun/playwright-utils for other recorded verdicts.
- Review the evidence and your use of @empiricalrun/playwright-utils@0.62.1 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.