registry / @hmharness/cli / 0.18.13
@hmharness/cli@0.18.13
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-aiInspected source shows no install hook or concrete malicious behavior. The flagged network and child-process operations serve the CLI’s update reminder and local web daemon.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The version check runs from the interactive REPL; the daemon starts when the web frontend is invoked.
Impact
No confirmed attack surface was established by these behaviors.
Mechanism
The update check fetches npm dist-tags and caches the latest version. The daemon launches the CLI’s web command and probes its localhost endpoint.
AI rationale
Inspected source shows no install hook or concrete malicious behavior. The flagged network and child-process operations serve the CLI’s update reminder and local web daemon.
Evidence
package.jsondist/main.jsdist/update-check.jsdist/web-daemon.js
Network endpoints2
registry.npmjs.org/-/package/@hmharness/cli/dist-tags127.0.0.1:${port}/api/state
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 defines only a build script and lists HMHarness packages as dependencies; it has no install lifecycle hook.
- dist/main.js starts the update reminder in the interactive REPL.
- dist/update-check.js fetches version tags from the npm registry and caches the result.
- dist/web-daemon.js starts the CLI’s web command as a detached child and probes the local server.
Evidence against
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 · L31115// npm is pull-based; the update reminder is a cached (1/day) registry
// check printed when resolved - never blocks, never nags offline
const { notifyUpdate } = await import("./update-check.js");
const { createRequire } = await import('node:module');
const CURRENT_VERSION = createRequire(import.meta.url)('../package.json').vers
Low
Ai Review Evidence
dist/main.js starts the update reminder in the interactive REPL.
dist/main.jsView on unpkg · L115dist/web-daemon.jsView 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.13.
See all versions of @hmharness/cli for other recorded verdicts.
- Review the evidence and your use of @hmharness/cli@0.18.13 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.