@indigoai-us/hq-cli@5.345.134
HQ by Indigo management CLI — modules and cloud sync
AI Security Review
scanned 8d ago · by lpm-firewall-aiSource inspection found no concrete malicious behavior. The flagged lifecycle action is conditional maintenance of an existing daemon, and the inspected agent configuration and credential handling are consistent with the package's CLI and capacity-collection functions.
Decision evidence
public snapshot- package.json runs a postinstall script that invokes the CLI with --if-stale; the handler skips reinstalling unless an existing daemon version or node path needs an update.
- The flagged agent-related paths handle HQ project state, read settings or credential-file presence, filter sensitive paths, or enumerate policy directories; the inspected excerpts show no unconsented broad agent configuration mutation.
- The startup recovery and staged update code concern CLI registration and a constrained npm global package layout; rescue resolves a target from invocation options.
- The Claude OAuth collector sends a bearer token to Anthropic's usage endpoint and uses Anthropic's token endpoint for refresh.
- The scaffold hook validates policy frontmatter, and the schema module adapts output schemas for the workflow runner.
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.134.
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.134 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.