registry / @empiricalrun/playwright-utils / 0.60.2
@empiricalrun/playwright-utils@0.60.2
Playwright utils for test code repos of our customers
AI Security Review
scanned 28d ago · by lpm-firewall-aiThe package manifest has no install lifecycle hook, and the reviewed behaviors align with test reporting and Playwright utilities. Dynamic execution in the overlay cache is limited in the inspected code to a matching cached entry and caller-provided page, with no confirmed attack surface.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A caller invokes the corresponding reporter, webhook, test-runner, or overlay-cache function.
Impact
No package-controlled credential theft, hidden exfiltration, or other confirmed attack effect was established.
Mechanism
The code merges reports, calls named test webhook providers, runs test tooling, and executes cached overlay code against a provided page.
AI rationale
The package manifest has no install lifecycle hook, and the reviewed behaviors align with test reporting and Playwright utilities. Dynamic execution in the overlay cache is limited in the inspected code to a matching cached entry and caller-provided page, with no confirmed attack surface.
Decision evidence
public snapshotAI called this Clean at 84.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json points to the package entrypoint and contains no install lifecycle hook.
- The local reporter runs Playwright report merging in response to its function call.
- Webhook helpers create and query explicitly selected test webhook providers.
- The oracle script imports process and filesystem tools for its test-runner purpose.
- The overlay cache executes code previously stored for matching browser elements.
Evidence against
- The cache helper uses dynamic function construction to execute cached code, but the inspected code ties it to matching overlay entries and a supplied Playwright page; no broader attack behavior was established.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
Source & flagged code
9 flaggeddist/reporter/local-test.jsView file
6exports.mergeForLocalTest = mergeForLocalTest;
L7: const child_process_1 = require("child_process");
L8: const path_1 = __importDefault(require("path"));
High
Child Process
Package source references child process execution.
dist/reporter/local-test.jsView on unpkg · L613try {
L14: (0, child_process_1.execFileSync)("npx", ["playwright", "merge-reports", outputDir, "--reporter", "html,json"], {
L15: cwd: currentWorkingDir,
High
Runtime Package Install
Package source invokes a package manager install command at runtime.
dist/reporter/local-test.jsView on unpkg · L13dist/kv.jsView file
3exports.KVClient = void 0;
L4: const api_worker_client_1 = require("./api-worker-client");
L5: class KVClient {
Medium
Findings
3 Critical6 High4 Medium5 Low
CriticalCredential Exfiltrationdist/webhook.js
CriticalTrigger Reachable Dangerous Capabilitydist/webhook.js
CriticalPrevious Version Dangerous Deltadist/test/scripts/pw-locator-patch/dismiss-overlays/cache.js
HighChild Processdist/reporter/local-test.js
HighShell
HighTrigger Reachable Credential Exfiltrationdist/webhook.js
HighTrigger Reachable External Post Callbackdist/webhook.js
HighRuntime Package Installdist/reporter/local-test.js
HighSemantic Analysis Limitedupstream-oracle/run.mjs#virtual:normalized:round1
MediumDynamic Requiredist/kv.js
MediumNetwork
Medium
Affected versions and remediation
This report applies to @empiricalrun/playwright-utils@0.60.2.
See all versions of @empiricalrun/playwright-utils for other recorded verdicts.
- Review the evidence and your use of @empiricalrun/playwright-utils@0.60.2 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.