registry / @hmharness/cli / 0.20.2
@hmharness/cli@0.20.2
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 package has no install lifecycle hook, but TUI startup can silently update its global CLI installation. This is a concrete, package-aligned capability that warrants a warning, not a publish block.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Starting the TUI when a newer registry release is available, unless auto-update is disabled in configuration.
Impact
The global CLI installation may be replaced by a newer release without an explicit update command.
Mechanism
The CLI checks the npm registry and launches a detached global npm install for the latest @hmharness/cli release.
AI rationale
The package has no install lifecycle hook, but TUI startup can silently update its global CLI installation. This is a concrete, package-aligned capability that warrants a warning, not a publish block.
Evidence
dist/main.jsdist/tui.jsdist/update-check.js<user global npm installation>
Network endpoints1
registry.npmjs.org/-/package/@hmharness/cli/dist-tags
Decision evidence
public snapshotAI called this Suspicious at 85.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The `tui` CLI command starts the TUI.
- TUI startup automatically checks for updates unless `tui.autoUpdate` is explicitly false.
- The check contacts the npm registry for this package’s latest release.
- When an update is available, the code launches a detached global npm install of this package.
Evidence against
- The update is limited to `@hmharness/cli` and uses `registry.npmjs.org`.
- The manifest has no install lifecycle hook; the automatic update runs during TUI startup.
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 · L33907if (cmd === 'tui') {
await initHome();
// tui(yes, noWeb): inside the TTY check the TUI auto-links the web UI
const { tui } = await import("./tui.js");
Medium
dist/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 High6 Medium4 Low
HighCopied Package Dependency Bridgedist/main.js
HighPrevious Version Dangerous Deltadist/tui.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumAi Review Evidencedist/main.js
MediumAi Review Evidencedist/tui.js
MediumAi Review Evidencedist/update-check.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @hmharness/cli@0.20.2.
See all versions of @hmharness/cli for other recorded verdicts.
- Review the evidence and your use of @hmharness/cli@0.20.2 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.