@indigoai-us/hq-cli@5.345.69
HQ by Indigo management CLI — modules and cloud sync
AI Security Review
scanned 13d ago · by lpm-firewall-aiStatic inspection found an automatic postinstall path that can create or refresh a per-user background service, so a warning is warranted for persistence risk. The reviewed source does not establish stealth, data theft, or destructive behavior.
Decision evidence
public snapshot- `package.json` runs a postinstall script that launches the installed CLI with the daemon install command.
- When daemon state has no recorded version, the stale check treats it as needing installation; the installer writes a per-user systemd service.
- The CLI’s install command routes the postinstall invocation into that stale check. This creates an automatic persistence risk, though the service is identified as the HQ mesh daemon.
- The inspected agent-integration excerpts show local session-state writes, settings reads, credential-file existence checks, and policy-directory reads; these excerpts do not establish an agent-control attack.
- The service is named and described as the HQ mesh daemon, and the postinstall path uses an explicit stale-version check; inspected source does not show stealth, exfiltration, or destructive behavior.
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.69.
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.69 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.