@metaphi-ai/hum@0.2.61
Hum: a self-improving coding agent for your terminal.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe automatic postinstall path can execute a remotely fetched installer when uv is absent, creating a concrete install-time execution risk. The inspected code ties this to setting up the package’s version-matched Python core and does not establish malicious behavior, so warn rather than block.
Static reason
One or more suspicious static signals were detected.
Trigger
Package installation invokes the postinstall hook when the matching core is not already installed.
Impact
The hook can run downloaded installer code and create a Python environment in the user’s .hum directory during package installation.
Mechanism
The hook calls installCore; if uv is unavailable, that function pipes a script from astral.sh to sh on Unix or executes the corresponding PowerShell installer on Windows, then installs the version-matched Python core.
AI rationale
The automatic postinstall path can execute a remotely fetched installer when uv is absent, creating a concrete install-time execution risk. The inspected code ties this to setting up the package’s version-matched Python core and does not establish malicious behavior, so warn rather than block.
Evidence
package.jsonscripts/postinstall.jsdist/install.mjs
Network endpoints2
astral.sh/uv/install.shastral.sh/uv/install.ps1
Decision evidence
public snapshotAI called this Suspicious at 86.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- package.json runs scripts/postinstall.js automatically after installation.
- The postinstall path installs the version-matched Python core when it is missing.
- If uv is unavailable, the installer runs a shell command that pipes a script fetched from astral.sh directly to sh.
- The installer creates a Python environment under the user’s .hum directory and installs hum-cli into it.
Evidence against
- The hook skips core installation when the matching version is already installed.
- The installer pins hum-cli to the package version by default and records the result under the user’s .hum directory.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
9 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node scripts/postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/install.mjsView file
1// src/install.js
L2: import { spawnSync } from "node:child_process";
L3: import fs from "node:fs";
High
Findings
5 High6 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processdist/install.mjs
HighShelldist/install.mjs#virtual:normalized:round1
HighCross File Remote Execution Contextdist/install.mjs
HighSemantic Analysis Limiteddist/install.mjs#virtual:normalized:round1
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requirebin/hum.js
MediumEnvironment Vars
MediumOversized Source Filedist/cli.mjs
MediumOversized Cli Entrypointdist/cli.mjs
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
Affected versions and remediation
This report applies to @metaphi-ai/hum@0.2.61.
See all versions of @metaphi-ai/hum for other recorded verdicts.
- Review the evidence and your use of @metaphi-ai/hum@0.2.61 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.