registry / @hmharness/cli / 0.23.30
@hmharness/cli@0.23.30
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 or runtime self-dependency, and the flagged process execution serves explicit CLI daemon commands. The board installation writes are part of a separately invoked installer; inspected source did not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user invokes the CLI service command or runs the board installer.
Impact
The inspected behavior supports the package’s CLI and board setup functions; no confirmed malicious effect was established.
Mechanism
The daemon helpers detach the corresponding CLI command; the board installer writes launchers and setup files as part of its invoked installation flow.
AI rationale
The manifest has no install lifecycle hook or runtime self-dependency, and the flagged process execution serves explicit CLI daemon commands. The board installation writes are part of a separately invoked installer; inspected source did not establish malicious behavior.
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines only a build script and lists same-version first-party runtime dependencies; no install lifecycle hook or runtime self-dependency appears.
- The board installer documents explicit invocation with `node install-kaihongos.cjs`; its launcher and heal-layer writes belong to that installer flow.
- The web daemon starts the CLI’s web command as a detached child and records daemon state under the application home.
- The extension daemon starts the CLI’s extension serve command as a detached child and records daemon state under the application home.
- The inspected source supports user-invoked CLI services and setup, with no confirmed attack behavior.
Evidence against
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggedboard/install-kaihongos.cjsView file
35const https = require('https');
L36: const { spawnSync } = require('child_process');
L37:
High
Child Process
Package source references child process execution.
board/install-kaihongos.cjsView on unpkg · L35339log('first run: creating config skeleton at ' + HMH_HOME);
L340: const r = spawnSync(nodeBin, [path.join(NM, '@hmharness', 'cli', 'dist', 'main.js'), 'init'], {
L341: encoding: 'utf8', env: Object.assign({}, process.env, { HMH_HOME, HOME: BOARD_HOME }),
L342: });
...
L349: console.log(' 2. hmh check # verify toolchain');
L350: console.log(' 3. hmh tui # or: hmh web start → http://127.0.0.1:7788');
L351: console.log('pitfalls & details: docs/KAIHONGOS.md');
High
Same File Env Network Execution
A single source file combines environment access, network access, and code or shell execution; review context before blocking.
board/install-kaihongos.cjsView on unpkg · L339dist/web-daemon.jsView file
Findings
5 High3 Medium4 Low
HighChild Processboard/install-kaihongos.cjs
HighShelldist/web-daemon.js
HighSame File Env Network Executionboard/install-kaihongos.cjs
HighCopied Package Dependency Bridgedist/main.js
HighPrevious Version Dangerous Deltadist/extension-daemon.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @hmharness/cli@0.23.30.
See all versions of @hmharness/cli for other recorded verdicts.
- Review the evidence and your use of @hmharness/cli@0.23.30 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.