registry / @hmharness/cli / 0.19.7
@hmharness/cli@0.19.7
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 network and process behaviors support package-aligned update functionality, and the manifest has no install lifecycle hook. No concrete attack behavior was established.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Launching the interactive TUI can start the update check and automatic update; the package manifest has no install lifecycle hook.
Impact
The inspected behavior can update the CLI from its configured registry; no unrelated recipient or payload execution was established.
Mechanism
The updater queries the npm registry for @hmharness/cli and constructs a global npm install command scoped to that package.
AI rationale
The flagged network and process behaviors support package-aligned update functionality, and the manifest has no install lifecycle hook. No concrete attack behavior was established.
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 defines only a build script and dependencies; no install lifecycle hook is present.
- The main entrypoint uses the update-check module for a nonblocking update notice.
- The TUI invokes its updater during startup, with a config option to disable automatic updates.
- The updater checks the npm registry for this package and constructs an install command scoped to @hmharness/cli.
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 · L33118// check printed when resolved - never blocks, never nags offline
const { notifyUpdate } = await import("./update-check.js");
const { createRequire } = await import('node:module');
const CURRENT
Low
Ai Review Evidence
The main entrypoint uses the update-check module for a nonblocking update notice.
dist/main.jsView on unpkg · L118dist/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
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencedist/main.js
LowAi Review Evidencedist/tui.js
Affected versions and remediation
This report applies to @hmharness/cli@0.19.7.
See all versions of @hmharness/cli for other recorded verdicts.
- Review the evidence and your use of @hmharness/cli@0.19.7 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.