registry / @hmharness/cli / 0.19.3
@hmharness/cli@0.19.3
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 no install lifecycle hook or concrete malicious behavior. Network access is package-aligned, and the inspected TUI file and process actions are tied to user interactions.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Interactive CLI startup, the stats command, or user-invoked TUI actions.
Impact
No confirmed attack surface was established; inspected requests do not transmit user credentials or files.
Mechanism
The CLI checks its own npm package metadata and can retrieve public package download counts; the TUI can open a draft in the configured editor and set up remote access when requested.
AI rationale
Source inspection found no install lifecycle hook or concrete malicious behavior. Network access is package-aligned, and the inspected TUI file and process actions are tied to user interactions.
Network endpoints2
registry.npmjs.org/-/package/@hmharness/cli/dist-tagsapi.npmjs.org/downloads/point/
Decision evidence
public snapshotAI called this Clean at 95.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json has only a build script and declares matching-version @hmharness runtime dependencies.
- dist/main.js loads its update reminder from a separate module and reads this package’s own version.
- dist/tui.js writes a draft for the user-invoked external editor and offers remote setup through explicit slash commands.
- dist/update-check.js checks the package’s own npm registry metadata; dist/npm-stats.js fetches public download counts.
Evidence against
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
5 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 { createReq
Low
Ai Review Evidence
dist/main.js loads its update reminder from a separate module and reads this package’s own version.
dist/main.jsView on unpkg · L1151104const { startServer } = await import('@hmharness/web');
const { createRequire: cr } = await import('node:module');
const ver = cr(import.meta.url)('../package.json').version ?? '';
await startServer({
port: Number.isFinite(por
Low
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 Dependency Evidencepackage.json
LowAi Review Evidencedist/main.js
LowAi Review Evidencedist/main.js
Affected versions and remediation
This report applies to @hmharness/cli@0.19.3.
See all versions of @hmharness/cli for other recorded verdicts.
- Review the evidence and your use of @hmharness/cli@0.19.3 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.