@hmharness/cli@0.18.8
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 update behavior is package-aligned: registry checks and optional automatic installation of this CLI's own release. The scanner's structural and wildcard-dependency signals do not establish a concrete attack.
Decision evidence
public snapshot- package.json has no install lifecycle hook and depends on related @hmharness packages.
- The interactive REPL makes a registry version check and displays an update reminder.
- The web daemon probes only the local 127.0.0.1 endpoint and starts the CLI entrypoint as a child process.
- The TUI auto-update installs a newer release of this same CLI from the npm registry; setting tui.autoUpdate to false switches to a reminder.
Source & flagged code
4 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/main.jsView on unpkg · L31The interactive REPL makes a registry version check and displays an update reminder.
dist/main.jsView on unpkg · L115Findings
Affected versions and remediation
This report applies to @hmharness/cli@0.18.8.
See all versions of @hmharness/cli for other recorded verdicts.
- Review the evidence and your use of @hmharness/cli@0.18.8 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.