@hmharness/cli@0.23.3
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-aiInspected the manifest, executable entrypoint, flagged TUI source, and referenced update helper. Their lifecycle, registry-check, and explicit pairing behaviors provide no concrete attack surface.
Decision evidence
public snapshot- package.json defines only a build script and lists matching @hmharness dependencies; it has no install lifecycle hook.
- dist/main.js runs an update reminder in the interactive REPL.
- dist/update-check.js fetches npm dist-tags from the package’s registry and caches the result under the user home directory.
- dist/tui.js performs the remote pairing flow only after the user enters a /remote command; it contacts the local web daemon.
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 runs an update reminder in the interactive REPL.
dist/main.jsView on unpkg · L117Findings
Affected versions and remediation
This report applies to @hmharness/cli@0.23.3.
See all versions of @hmharness/cli for other recorded verdicts.
- Review the evidence and your use of @hmharness/cli@0.23.3 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.