@hmharness/cli@0.23.50
hmharness command line: one-shot tasks, an interactive REPL, a fullscreen TUI, the web frontend, and direct tool invocation.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe web-start path silently launches recurring evolution and fine-tuning that use the configured provider key and can create paid jobs. The thresholds and opt-out reduce frequency but do not provide consent for automatic model use, data upload, or spending.
Decision evidence
public snapshot- Starting `hmh web` silently starts the evolution daemon; the source says the user does not trigger `hmh evolve` manually.
- The daemon runs `evolve` after startup and on a six-hour schedule; its source describes 40+ model calls per cycle.
- After each evolution cycle, the daemon invokes `auto-finetune --submit`, which uses the configured provider key to upload training data and create a paid fine-tuning job.
- Fine-tuning is gated on at least 50 labels, a cooldown, no active job, and can be disabled with `finetune.auto=false`.
- The package manifest defines only a build script and no install lifecycle hooks.
- The fine-tuning backend is resolved from the user's configured chat provider and its base URL.
- Automatic fine-tuning has label, cooldown, active-job, and opt-out gates.
- The package has no install, preinstall, or postinstall script.
Source & flagged code
18 flaggedPackage source references child process execution.
board/install-kaihongos.cjsView on unpkg · L38Source file is highly similar to a previously finalized malicious package; route for source-aware review.
board/install-kaihongos.cjsView on unpkgSource file is highly similar to a previously finalized malicious package; route for source-aware review.
dist/web-daemon.jsView on unpkgPackage source references dynamic require/import behavior.
board/board-defaults.cjsView on unpkg · L35A manifest entrypoint or package-local install chain reaches persistence behavior.
dist/extension-daemon.jsView on unpkg · L10Source file is highly similar to a previously finalized malicious package; route for source-aware review.
dist/extension-daemon.jsView on unpkgSource writes installer persistence such as shell profile or service configuration.
dist/extension-daemon.jsView on unpkg · L10A single source file combines environment access, network access, and code or shell execution; review context before blocking.
board/heal-tree.cjsView on unpkg · L27Source file is highly similar to a previously finalized malicious package; route for source-aware review.
board/heal-tree.cjsView on unpkgPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/main.jsView on unpkg · L33Source file is highly similar to a previously finalized malicious package; route for source-aware review.
dist/main.jsView on unpkgA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/extension-daemon.js#virtual:normalized:round1View on unpkgSource file is highly similar to a previously finalized malicious package; route for source-aware review.
dist/tui.jsView on unpkgSource file is highly similar to a previously finalized malicious package; route for source-aware review.
dist/evolution-daemon.jsView on unpkgSource file is highly similar to a previously finalized malicious package; route for source-aware review.
dist/update-check.jsView on unpkgSource file is highly similar to a previously finalized malicious package; route for source-aware review.
dist/acp-serve.jsView on unpkgThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/tui-mouse.jsView on unpkgFindings
Affected versions and remediation
This report applies to @hmharness/cli@0.23.50.
See all versions of @hmharness/cli for other recorded verdicts.
- Avoid installing @hmharness/cli@0.23.50. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.