@metaphi-ai/hum@0.1.86
Hum: a self-improving coding agent for your terminal.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package has a real install-time remote-code supply-chain surface, so it should warn. It does not meet the stated blocking condition because the inspected code is a transparent same-product installer confined to its own user-home area and has no self-dependency chain or confirmed theft.
Decision evidence
public snapshot- An npm postinstall automatically invokes the core installer.
- When uv is absent, installation pipes a remote script into a shell with no integrity pinning.
- The installer then installs the external hum-cli Python package into the user home directory.
- The installed Python package is version-pinned to this package release by default.
- The inspected code writes under ~/.hum and does not modify the consumer project or AI-agent configuration.
- No browser credential harvesting or exfiltration logic was found in the inspected package source.
Source & flagged code
11 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.86.
See all versions of @metaphi-ai/hum for other recorded verdicts.
- Review the evidence and your use of @metaphi-ai/hum@0.1.86 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.