@pawlogic/dl@0.38.0
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe flagged process execution and network behavior map to the package’s CLI functions and configured service RPCs. The manifest has no lifecycle hooks, and inspected sources do not establish malicious behavior.
Decision evidence
public snapshot- package.json defines CLI entrypoints, pins playwright-core, and has no lifecycle scripts; the dependency manifest also has no install scripts.
- The flagged shell execution is part of the selected local Python transform command, which returns its output through the CLI.
- Sandbox API requests require the configured callback URL and proxy token; billing requests send that token to the configured service endpoint.
- Updater reports send outcome and runtime identifiers to the configured callback RPC endpoint using the existing proxy token.
- The dependency entrypoints, bundles, and type files describe Playwright browser automation and its browser protocol.
Source & flagged code
8 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.38.0.
See all versions of @pawlogic/dl for other recorded verdicts.
- Review the evidence and your use of @pawlogic/dl@0.38.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.