@indigoai-us/hq-cli@5.345.106
HQ by Indigo management CLI — modules and cloud sync
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe automatic lifecycle-triggered service setup creates a real persistence risk, so this package merits a warning. The inspected behavior is package-aligned daemon setup and does not establish a concrete malicious attack.
Decision evidence
public snapshot- package.json runs a daemon setup script during postinstall.
- The script invokes this package’s CLI to install the mesh daemon when it is stale.
- A missing recorded daemon version counts as stale, and that path invokes service installation.
- Service installation writes user-level startup units or a scheduled task and activates them.
- The flagged agent-related locations read configuration, filter policy paths, inspect credential-file size without reading credential contents, or write session state; they do not establish credential disclosure or an agent-control takeover.
- The daemon is a package-owned HQ mesh component, and the inspected code installs it through platform service managers.
- The flagged agent-related code shows configuration and project-state handling, with no unrelated credential recipient in the inspected locations.
Source & flagged code
17 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references child process execution.
dist/startup-registration.jsView on unpkg · L18Findings
Affected versions and remediation
This report applies to @indigoai-us/hq-cli@5.345.106.
See all versions of @indigoai-us/hq-cli for other recorded verdicts.
- Review the evidence and your use of @indigoai-us/hq-cli@5.345.106 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.