@hmharness/cli@0.20.1
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 inspected runtime behavior is consistent with the package’s CLI functions. The local pairing request and explicit transcript export do not establish a malicious attack surface.
Decision evidence
public snapshot- package.json defines only a build script and lists first-party HMHarness dependencies; it has no install lifecycle hook.
- dist/main.js identifies the executable as the HMHarness terminal frontend and lists user-invoked CLI commands.
- dist/tui.js requests pairing information from the local web daemon when handling a TUI command.
- dist/tui.js exports the current session transcript to the user’s HMHarness exports directory on an explicit command.
Source & flagged code
5 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/main.jsView on unpkg · L33dist/main.js identifies the executable as the HMHarness terminal frontend and lists user-invoked CLI commands.
dist/main.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @hmharness/cli@0.20.1.
See all versions of @hmharness/cli for other recorded verdicts.
- Review the evidence and your use of @hmharness/cli@0.20.1 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.