@metaphi-ai/hum@0.1.22
Hum (हम): a self-improving coding agent for your terminal.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe lifecycle behavior is package-aligned setup of a version-matched engine in a dedicated directory, with cleanup limited to the package's earlier launcher shims. The scanner's credential and shell indicators do not establish credential collection or a malicious execution chain in the inspected source.
Decision evidence
public snapshot- The npm postinstall creates an isolated Python engine under HUM_HOME or ~/.hum and installs the matching hum-cli version.
- The CLI starts that engine when the user invokes hum; npm-layout update checks show an update command rather than starting a background installer.
- The installer removes an earlier hum-cli tool installation and its own launcher shims when present.
- The postinstall can bootstrap uv through a shell command and fetch the matching engine package, so installation performs network-backed setup.
- The bundle contains an update endpoint, but its update flow does not automatically install updates for npm-layout installations.
Source & flagged code
10 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.22.
See all versions of @metaphi-ai/hum for other recorded verdicts.
- Review the evidence and your use of @metaphi-ai/hum@0.1.22 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.