@hmharness/cli@0.23.37
hmharness command line: one-shot tasks, an interactive REPL, a fullscreen TUI, the web frontend, and direct tool invocation.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected dependencies have ordinary build scripts and package-aligned exports. The flagged installer, update, and process behavior is consistent with the CLI's setup and runtime functions, with no concrete attack behavior established.
Decision evidence
public snapshot- The manifest declares only a build script and pins its first-party runtime dependencies to version 0.23.37.
- The board installer is a separately invoked setup command; its source performs board installation and launcher setup.
- The agent runner reads project guidance files and passes the result into its system prompt, a normal agent feature.
- The inspected first-party dependency manifests declare build-only scripts, and their entrypoints export product APIs.
- The web daemon checks that a port owner is one of its own web daemons before terminating it.
- No package install lifecycle hook or malicious install-time action was identified.
- The flagged network and subprocess behavior is consistent with package updates, explicit board setup, and local daemon management.
Source & flagged code
5 flaggedPackage source references child process execution.
board/install-kaihongos.cjsView on unpkg · L35A single source file combines environment access, network access, and code or shell execution; review context before blocking.
board/install-kaihongos.cjsView on unpkg · L339Findings
Affected versions and remediation
This report applies to @hmharness/cli@0.23.37.
See all versions of @hmharness/cli for other recorded verdicts.
- Review the evidence and your use of @hmharness/cli@0.23.37 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.