@pawlogic/dl@0.41.0
AI Security Review
scanned 16h ago · by lpm-firewall-aiThe package’s wrapper-triggered update reporting sends sandbox hostname and user, project, prompt, and tool-call identifiers to the callback service. This is identifying runtime telemetry, so the package is suspicious rather than malicious; the inspected code does not show credential theft or unrelated file collection.
Decision evidence
public snapshot- The package’s shell helper is described as running synchronously before the `dl` CLI on each wrapper invocation.
- The helper sends a POST to `${CALLBACK_SERVER_URL}/sandbox-rpc/dl/selfupdate-event` using the sandbox token.
- The event includes the sandbox hostname, project ID, user ID, prompt ID, and tool-call ID; npm failure events may also include up to 200 bytes of stderr.
- The main CLI routes sandbox requests through the injected callback server and proxy token.
- The event is limited to update status and context fields; the inspected path does not show credentials or user files being collected.
- The package exposes CLI commands and depends on `playwright-core`, consistent with its browser automation purpose.
Source & flagged code
7 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dl.mjsView on unpkg · L1Source combines command execution, command-output handling, and outbound requests; review data flow before blocking.
dl.mjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @pawlogic/dl@0.41.0.
See all versions of @pawlogic/dl for other recorded verdicts.
- Review the evidence and your use of @pawlogic/dl@0.41.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.