@hmharness/cli@0.21.0
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 default TUI behavior silently initiates a global self-update, creating a supply-chain update risk that merits a warning. The package-scoped registry destination and user-started trigger do not establish malicious intent or justify blocking.
Decision evidence
public snapshot- The TUI starts automatic update logic by default when run; setting `tui.autoUpdate` to false changes it to a notice only.
- The updater installs a newer `@hmharness/cli` release globally from registry.npmjs.org in a detached process.
- The manifest defines no install lifecycle hooks; its only script is `build`.
- The update check targets this package’s own npm registry entry, and the install command is limited to the CLI package.
- The updater is reached through the user-started TUI, not through package installation or import alone.
Source & flagged code
5 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/main.jsView on unpkg · L33This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/tui.jsView on unpkgFindings
Affected versions and remediation
This report applies to @hmharness/cli@0.21.0.
See all versions of @hmharness/cli for other recorded verdicts.
- Review the evidence and your use of @hmharness/cli@0.21.0 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.