registry / @hmharness/cli / 0.18.12
@hmharness/cli@0.18.12
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 daemon behavior starts the CLI's own web service, and the update path targets this package through the npm registry. No concrete malicious behavior was established in the inspected source.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Starting the TUI, unless tui.autoUpdate is set to false.
Impact
The CLI may update itself in the background; inspected source does not establish a malicious payload or unrelated target.
Mechanism
It fetches the latest version from registry.npmjs.org and launches npm to install @hmharness/cli globally.
AI rationale
The flagged daemon behavior starts the CLI's own web service, and the update path targets this package through the npm registry. No concrete malicious behavior was established in the inspected source.
Evidence
package.jsondist/main.jsdist/web-daemon.jsdist/tui.jsdist/update-check.js
Network endpoints1
registry.npmjs.org/-/package/@hmharness/cli/dist-tags
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json contains no install lifecycle hook; its only script is the build.
- dist/main.js imports the local web-daemon helper as part of the CLI.
- dist/web-daemon.js starts a detached copy of the CLI for its local web service.
- dist/tui.js checks for updates when the TUI starts; setting tui.autoUpdate to false disables installation and leaves a reminder.
- dist/update-check.js checks the npm registry and builds an npm install command targeting @hmharness/cli.
Evidence against
- The TUI can automatically install a newer CLI release in the background when it starts; this is a package self-update through the npm registry.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
WildcardDependency
Source & flagged code
4 flaggeddist/main.jsView file
31package = @hmharness/cli; repositoryIdentity = hmharness; dependency = @hmharness/agent
L31: import { harmonyTools } from '@hmharness/domain-harmony';
L32: import { baseTools, buildRegistry, buildSystemPrompt, runAgentTask, strings } from '@hmharness/agent';
L33: 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 · L3128import { stopWebDaemon, startWebDaemon, hmhWebUp, readWebPid } from "./web-daemon.js";
import { chat, homeDir, resolvePro
Low
Ai Review Evidence
dist/main.js imports the local web-daemon helper as part of the CLI.
dist/main.jsView on unpkg · L28dist/web-daemon.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @hmharness/cli@0.14.24
matchedIdentity = npm:QGhtaGFybmVzcy9jbGk:0.14.24
similarity = 0.556
summary = stored previous version shares package body but lacks this dangerous source file
Findings
2 High4 Medium6 Low
HighCopied Package Dependency Bridgedist/main.js
HighPrevious Version Dangerous Deltadist/web-daemon.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumWildcard Dependency
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencedist/main.js
Affected versions and remediation
This report applies to @hmharness/cli@0.18.12.
See all versions of @hmharness/cli for other recorded verdicts.
- Review the evidence and your use of @hmharness/cli@0.18.12 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.