@agentdock/daemon@0.0.102
PC daemon + CLI for AgentDock — ACP abstraction, TransportHandler, process management
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe daemon automatically uploads activity derived from local agent history, including project and transcript paths, to its configured server. This is a privacy-sensitive telemetry behavior, so warn rather than block; the reviewed code does not establish credential theft or an unrelated collector.
Decision evidence
public snapshot- The usage watcher derives activity records containing local transcript file paths and project directories.
- The uploader sends activity statistics and a machine ID to the configured server’s `/v1/activity/upload` endpoint.
- The daemon starts periodic activity uploads after its initial scan when connected; the code does not show an explicit user opt-in gate.
- The upload destination comes from the daemon’s server endpoint, which may be configured or supplied by the package’s default brand settings.
- The manifest has no install lifecycle scripts; its CLI and import entry points are conventional for a daemon package.
- The process spawning, login autostart, and upgrade code support the package’s stated daemon purpose.
- The reviewed credential and upgrade paths did not show credentials being sent to an unrelated collector.
Source & flagged code
9 flaggedPackage source references child process execution.
dist/triggerUpgradeRpc.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @agentdock/daemon@0.0.102.
See all versions of @agentdock/daemon for other recorded verdicts.
- Review the evidence and your use of @agentdock/daemon@0.0.102 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.