registry / @hmharness/cli / 0.19.9
@hmharness/cli@0.19.9
hmharness command line: one-shot tasks, an interactive REPL, a fullscreen TUI, the web frontend, and direct tool invocation.
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe flagged behaviors inspected are consistent with the CLI’s own update and local pairing functions, and the manifest has no install lifecycle hook. No concrete malicious behavior was established.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Running the CLI REPL or TUI; the TUI’s update behavior runs unless disabled in configuration.
Impact
The package may update its own global CLI installation; inspected source did not show a malicious payload or unrelated recipient.
Mechanism
The update check queries the npm registry and may spawn npm to install a newer @hmharness/cli release. The pairing flow fetches status from 127.0.0.1.
AI rationale
The flagged behaviors inspected are consistent with the CLI’s own update and local pairing functions, and the manifest has no install lifecycle hook. No concrete malicious behavior was established.
Evidence
package.jsondist/main.jsdist/tui.jsdist/update-check.js
Network endpoints2
registry.npmjs.org/-/package/@hmharness/cli/dist-tags127.0.0.1
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines only a build script and lists same-version @hmharness dependencies; it has no install lifecycle hook.
- The CLI update check contacts the npm registry for this package’s latest release.
- The TUI can automatically install a newer @hmharness/cli release in the background when the TUI runs; this is package-aligned update behavior.
- The TUI pairing request targets the local web daemon at 127.0.0.1.
Evidence against
- Inspected entrypoint and flagged TUI code showed no credential harvesting, unrelated network recipient, or destructive behavior.
- The flagged subprocesses are tied to explicit editor, diff, clipboard, preference export, or package-update behavior.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggeddist/main.jsView file
33package = @hmharness/cli; repositoryIdentity = hmharness; dependency = @hmharness/agent
L33: import { harmonyTools } from '@hmharness/domain-harmony';
L34: import { baseTools, buildRegistry, buildSystemPrompt, runAgentTask, strings } from '@hmharness/agent';
L35: const DIM = (s) => `\x1b[2m${s}\x1b[0m`;
High
Copied Package Dependency Bridge
Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/main.jsView on unpkg · L33dist/tui.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @hmharness/cli@0.15.0
matchedIdentity = npm:QGhtaGFybmVzcy9jbGk:0.15.0
similarity = 0.500
summary = stored previous version shares package body but lacks this dangerous source file
High
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/tui.jsView on unpkg1721// 2026-09-21 product direction: updates are ZERO-ACTION - a newer version
// installs itself in the background (detached npm, next launch picks it
// up; never swaps files under the running process) and we only SAY so.
// Opt out with config.json tui.autoUpdate=false (falls back to the hint).
const { notifyUpdate, aut
Findings
2 High3 Medium7 Low
HighCopied Package Dependency Bridgedist/main.js
HighPrevious Version Dangerous Deltadist/tui.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencedist/update-check.js
LowAi Review Evidencedist/tui.js
Affected versions and remediation
This report applies to @hmharness/cli@0.19.9.
See all versions of @hmharness/cli for other recorded verdicts.
- Review the evidence and your use of @hmharness/cli@0.19.9 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.