@metaphi-ai/hum@0.1.11
Hum (हम): a self-improving coding agent for your terminal.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe automatic postinstall performs network-backed setup, but it provisions the matching first-party engine and its uv installer endpoint is explicit. The inspected CLI process behavior supports local engine operation; the scanner's browser credential and malware labels are not supported by the inspected source.
Decision evidence
public snapshot- The postinstall hook creates a Python environment under HUM_HOME or the user's .hum directory and installs the matching hum-cli release.
- If uv is absent, the installer runs its install script from astral.sh; this is an install-time network and execution behavior.
- The CLI starts the Hum engine as a child process and connects to it on localhost; inspected source shows no browser credential collection or unrelated credential destination.
- The install hook sets up the package's matching first-party engine and removes an older hum-cli tool installation when detected.
- The CLI's inspected process and socket behavior is tied to starting and communicating with the local engine.
Source & flagged code
9 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @metaphi-ai/hum@0.1.11.
See all versions of @metaphi-ai/hum for other recorded verdicts.
- Review the evidence and your use of @metaphi-ai/hum@0.1.11 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.