registry / @empiricalrun/playwright-utils / 0.60.4
@empiricalrun/playwright-utils@0.60.4
Playwright utils for test code repos of our customers
AI Security Review
scanned 28d ago · by lpm-firewall-aiThe required source paths show no install lifecycle behavior or covert attack chain. The scanner-flagged operations are tied to explicit utilities and use the package's reporting and webhook functionality.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A caller invokes a reporting, webhook, or attachment-cleanup function.
Impact
These actions support the package's test and reporting functions; no covert credential exposure or malicious mutation was identified.
Mechanism
The utilities merge reports, create or query webhook tokens through configured providers, and evict uploaded attachments after the configured size limit is exceeded.
AI rationale
The required source paths show no install lifecycle behavior or covert attack chain. The scanner-flagged operations are tied to explicit utilities and use the package's reporting and webhook functionality.
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json has no install lifecycle hook; its scripts are development and build commands.
- The local report merge runs Playwright through an explicit function call and writes report outputs in the supplied working directory.
- Webhook token creation and querying are exposed as explicit functions and use the selected provider flow.
- The upstream oracle creates temporary report output and configures a test run; it does not show install-time behavior.
- Attachment cleanup marks files as uploaded before evicting them when the configured size limit is exceeded.
- The API client requires a caller-supplied or configured Empirical API key and sends it as a bearer credential to its configured API base URL.
- Webhook token creation is conditional on calling the provider function and uses the provider proxy or a webhook.site API key.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
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/reporter/attachment-cleanup.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
MediumEnvironment Vars
Affected versions and remediation
This report applies to @empiricalrun/playwright-utils@0.60.4.
See all versions of @empiricalrun/playwright-utils for other recorded verdicts.
- Review the evidence and your use of @empiricalrun/playwright-utils@0.60.4 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.