registry / @pawlogic/dl / 0.37.1
@pawlogic/dl@0.37.1
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the flagged process and network capabilities are consistent with the command-line tools, browser automation dependency, and update reporting. The inspected source does not establish a concrete attack or unrelated credential transfer.
Static reason
One or more suspicious static signals were detected.
Trigger
A user invokes a packaged command; the update helper is described as running through a sandbox wrapper.
Impact
No concrete malicious effect was established from these behaviors.
Mechanism
The tools communicate with configured service endpoints. The helper sends update status, environment identifiers, and a bounded error tail to its configured callback service.
AI rationale
The manifest has no install lifecycle hook, and the flagged process and network capabilities are consistent with the command-line tools, browser automation dependency, and update reporting. The inspected source does not establish a concrete attack or unrelated credential transfer.
Network endpoints1
callback-server-z4umynwjcq-uc.a.run.app
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes the dl and ilands command-line tools, depends on playwright-core, and declares no install lifecycle script.
- The CLI selects Actionway or sandbox service configuration and uses an HTTP client for JSON requests; the inspected code does not establish unrelated credential forwarding.
- The update helper reports update status and selected environment identifiers to the configured callback service, with a bounded error tail; this is operational telemetry, not evidence of arbitrary command-output exfiltration.
- The declared dependency identifies itself as Playwright browser automation; its inspected entrypoints export the browser APIs, and the cited bundle and type files are dependency implementation and declarations.
Evidence against
Behavioral surface
ChildProcessEnvironmentVarsEvalNetwork
HighEntropyStringsMinifiedTrivialUrlStrings
Source & flagged code
8 flaggeddl.mjsView file
1#!/usr/bin/env node
L2: import e,{readFileSync as t,existsSync as i,mkdirSync as n,writeFileSync as r,chmodSync as o,realpathSync as s,rmSync as a,cpSync as c}from"node:fs";import l,{dirname as d,resolve ...
High
1#!/usr/bin/env node
L2: import e,{readFileSync as t,existsSync as i,mkdirSync as n,writeFileSync as r,chmodSync as o,realpathSync as s,rmSync as a,cpSync as c}from"node:fs";import l,{dirname as d,resolve ...
High
Same File Env Network Execution
A single source file combines environment access, network access, and code or shell execution; review context before blocking.
dl.mjsView on unpkg · L11#!/usr/bin/env node
L2: import e,{readFileSync as t,existsSync as i,mkdirSync as n,writeFileSync as r,chmodSync as o,realpathSync as s,rmSync as a,cpSync as c}from"node:fs";import l,{dirname as d,resolve ...
High
Command Output Exfiltration
Source combines command execution, command-output handling, and outbound requests; review data flow before blocking.
dl.mjsView on unpkg · L1Findings
5 High4 Medium5 Low
HighChild Processdl.mjs
HighSame File Env Network Executiondl.mjs
HighCommand Output Exfiltrationdl.mjs
HighSandbox Evasion Gated Capabilitydl.mjs
HighTrigger Reachable Command Output Exfiltrationdl.mjs
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperdl-npm-update.sh
MediumStructural Risk Force Deep Review
LowEvaldl.mjs
LowWeak Cryptodl.mjs
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @pawlogic/dl@0.37.1.
See all versions of @pawlogic/dl for other recorded verdicts.
- Review the evidence and your use of @pawlogic/dl@0.37.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.