registry / @hmharness/cli / 0.23.8
@hmharness/cli@0.23.8
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 manifest points to the expected CLI entrypoint and has no install lifecycle hook; the inspected flagged behaviors are conditional local export and a loopback pairing request. No concrete attack surface was established.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The CLI runs when invoked; the DPO export path is used only when its local data file is missing.
Impact
No malicious effect or external data disclosure was established from these inspected behaviors.
Mechanism
That path re-invokes the CLI to export local preference data. The TUI fetches pairing state from the local web daemon.
AI rationale
The manifest points to the expected CLI entrypoint and has no install lifecycle hook; the inspected flagged behaviors are conditional local export and a loopback pairing request. No concrete attack surface was established.
Evidence
home/evolution/dpo-pairs.jsonl
Network endpoints1
127.0.0.1:${DEFAULT_WEB_PORT}/api/pair-info
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json routes the executable and module entrypoint to dist/main.js and shows no install lifecycle hook.
- dist/main.js reads the local DPO pairs file and only attempts its export when that file is absent.
- dist/tui.js requests pairing information from the local web daemon at 127.0.0.1.
Evidence against
- The package repository metadata identifies the hmharness project.
- The inspected dynamic process launch is limited to exporting a missing local DPO data file; no unrelated recipient or install-time execution was identified.
- The TUI network request targets loopback for pairing state.
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 · L331612// pairs: reuse dpo-pairs.jsonl, exporting it fresh if absent (zero-config)
const pairsFile = join(home, 'evolution', 'dpo-pairs.jsonl');
try {
await readFile(pairsFile, 'utf8');
}
Low
Ai Review Evidence
dist/main.js reads the local DPO pairs file and only attempts its export when that file is absent.
dist/main.jsView on unpkg · L1612dist/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.23.8.
See all versions of @hmharness/cli for other recorded verdicts.
- Review the evidence and your use of @hmharness/cli@0.23.8 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.