@agentdock/daemon@0.0.95
PC daemon + CLI for AgentDock — ACP abstraction, TransportHandler, process management
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged persistence supports the package’s daemon function and only runs when credentials exist; telemetry starts disabled. Runtime package installation is part of the CLI’s explicit upgrade command, and no malicious data flow or unrelated execution was found.
Decision evidence
public snapshot- The manifest exposes a daemon library and CLI entry point.
- Autostart setup is called from daemon startup and is skipped without stored credentials or when AGENTDOCK_NO_AUTOSTART=1.
- The daemon’s telemetry collector is initialized disabled.
- The package-manager install occurs in the upgrader, which the CLI invokes for the explicit upgrade command.
- Daemon startup writes a login service or registry entry to keep the daemon running; this matches the package’s stated daemon purpose.
- The upgrade path downloads and installs a package at runtime, but it is tied to the explicit upgrade command.
Source & flagged code
9 flaggedPackage source references child process execution.
dist/zombieReaper.jsView on unpkg · L1Package source references weak cryptographic algorithms.
dist/subagentIds.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @agentdock/daemon@0.0.95.
See all versions of @agentdock/daemon for other recorded verdicts.
- Review the evidence and your use of @agentdock/daemon@0.0.95 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.