@metaphi-ai/hum@0.2.32
Hum: a self-improving coding agent for your terminal.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe postinstall performs conditional setup for the package’s own core, but it may execute a remote installer through a shell pipeline. That warrants a warning for the automatic remote-code installation surface; the inspected source does not establish a concrete attack.
Decision evidence
public snapshot- package.json registers a postinstall script that runs scripts/postinstall.js.
- The postinstall handler calls installCore when the requested core version is not installed.
- installCore runs a shell or PowerShell command that pipes a script from astral.sh directly to a shell when uv is absent.
- The installer creates a Python environment and installs the Hum core into a versioned directory under the user’s Hum home.
- The installer targets Hum’s own core and versioned package directories; the inspected code does not show mutation of a foreign or broad AI-agent control surface.
- The evidence shows no credential harvesting, unrelated data exfiltration, or destructive behavior.
Source & flagged code
5 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 unpkgPackage source references dynamic require/import behavior.
bin/hum.jsView on unpkg · L25Findings
Affected versions and remediation
This report applies to @metaphi-ai/hum@0.2.32.
See all versions of @metaphi-ai/hum for other recorded verdicts.
- Review the evidence and your use of @metaphi-ai/hum@0.2.32 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.