registry / @hmharness/cli / 0.22.4
@hmharness/cli@0.22.4
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 has no install lifecycle hook, and the inspected network and fine-tuning actions are user-invoked. Scanner signals alone do not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The reviewed remote pairing path runs when the user enters /remote; fine-tuning submission requires --submit.
Impact
No confirmed attack surface was established in these inspected paths.
Mechanism
The TUI starts its web daemon and fetches pairing information from localhost. The CLI gates fine-tuning job creation behind an explicit flag.
AI rationale
The manifest has no install lifecycle hook, and the inspected network and fine-tuning actions are user-invoked. Scanner signals alone do not establish malicious behavior.
Evidence
package.jsondist/main.jsdist/tui.js
Network endpoints1
127.0.0.1:${DEFAULT_WEB_PORT}/api/pair-info
Decision evidence
public snapshotAI called this Clean at 84.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines only a build script and pins the runtime @hmharness dependencies to the same release.
- dist/main.js is the CLI entrypoint; its fine-tuning submission path requires the explicit --submit flag.
- dist/tui.js handles remote pairing only after the user enters a /remote command and requests pairing information from the local web server.
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 · L331587if (!rest.includes('--submit')) {
// files staged; the daemon submits automatically on its next cycle,
// or the user can fire it now
stdout.write('\n
Low
Ai Review Evidence
dist/main.js is the CLI entrypoint; its fine-tuning submission path requires the explicit --submit flag.
dist/main.jsView on unpkg · L1587dist/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 Dependency Evidencepackage.json
LowAi Review Evidencedist/main.js
LowAi Review Evidencedist/tui.js
Affected versions and remediation
This report applies to @hmharness/cli@0.22.4.
See all versions of @hmharness/cli for other recorded verdicts.
- Review the evidence and your use of @hmharness/cli@0.22.4 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.