registry / @hmharness/cli / 0.19.4
@hmharness/cli@0.19.4
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-aiSource inspection found a package-aligned updater reached by the explicit TUI command, which installs only this CLI package from the npm registry. The scanner hints do not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user runs the hmh tui command; the TUI performs its update check during startup.
Impact
A newer CLI release may replace the installed CLI; no unrelated package mutation or malicious behavior was established.
Mechanism
The updater obtains the latest package version from the npm registry and launches npm to install @hmharness/cli at that version. The TUI configuration can disable automatic updating.
AI rationale
Source inspection found a package-aligned updater reached by the explicit TUI command, which installs only this CLI package from the npm registry. The scanner hints do not establish malicious behavior.
Evidence
package.jsondist/main.jsdist/tui.jsdist/update-check.js
Network endpoints1
registry.npmjs.org/-/package/@hmharness/cli/dist-tags
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json identifies the package and points its CLI entrypoint to dist/main.js.
- dist/main.js invokes the TUI only for the user-requested tui command.
- dist/tui.js checks for updates during TUI startup; auto-update can be disabled in configuration.
- dist/update-check.js installs only a newer @hmharness/cli release from the npm registry. The update behavior is package-aligned and user-invoked.
Evidence against
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 · L33907tui') {
await initHome();
// tui(yes, noWeb): inside the TTY check the TUI auto-links the web UI
const { tui } = await import("./tui.js");
await tui(yes, rest
Low
Ai Review Evidence
dist/main.js invokes the TUI only for the user-requested tui command.
dist/main.jsView on unpkg · L907dist/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
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
LowAi Review Evidencepackage.json
LowAi Review Evidencedist/main.js
LowAi Review Evidencedist/tui.js
Affected versions and remediation
This report applies to @hmharness/cli@0.19.4.
See all versions of @hmharness/cli for other recorded verdicts.
- Review the evidence and your use of @hmharness/cli@0.19.4 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.