@pawlogic/dl@0.17.0
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo registry lifecycle hook is present, so the evidence does not meet the install-hook blocking threshold. The runtime self-update and telemetry behavior remains a real supply-chain risk when used by its intended wrapper.
Decision evidence
public snapshot- The shipped updater installs a tag-selected release of its own package globally with npm.
- It relinks command shims and overwrites a persistent updater script after installation.
- It sends environment-derived project, user, prompt, tool-call, and sandbox identifiers to an environment-configured callback endpoint.
- package.json has no preinstall, install, postinstall, or other lifecycle script.
- The updater is not invoked by the package manifest; activation requires an external wrapper or an explicit CLI action.
- No source-established fixed exfiltration host or credential harvesting was found.
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.17.0.
See all versions of @pawlogic/dl for other recorded verdicts.
- Review the evidence and your use of @pawlogic/dl@0.17.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.