@agentdock/daemon@0.0.97
PC daemon + CLI for AgentDock — ACP abstraction, TransportHandler, process management
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe flagged execution, network, and persistence primitives implement the daemon's runtime behavior with pairing and local authentication controls. Static inspection found no concrete malicious chain, install-hook abuse, or unrelated credential recipient.
Decision evidence
public snapshot- package.json has no install lifecycle hooks or runtime self-dependency; its entrypoints expose the daemon library and CLI.
- Upgrade commands implement package updates, validate CLI registry input, and guard session interruption.
- dist/ensureDaemon.js launches the local daemon and sends authenticated registration requests to loopback, without command-output exfiltration.
- Autostart configures this daemon's login service and skips setup when credentials are absent or autostart is disabled.
- The local control server binds to loopback and requires bearer authentication for RPC requests.
- Pairing credentials are stored by server URL; endpoint-specific lookup returns only that server's credentials.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/triggerUpgradeRpc.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @agentdock/daemon@0.0.97.
See all versions of @agentdock/daemon for other recorded verdicts.
- Review the evidence and your use of @agentdock/daemon@0.0.97 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.