@metaphi-ai/hum@0.2.39
Hum: a self-improving coding agent for your terminal.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe automatic install path executes a remote installer when uv is missing, creating a concrete but product-related remote execution risk. The inspected source does not establish a malicious payload or justify blocking publication.
Static reason
One or more suspicious static signals were detected.
Trigger
The npm postinstall hook runs when the package is installed and the matching core version is not already installed.
Impact
The remote installer executes with the installer's user privileges; the inspected code does not establish malicious behavior by that installer.
Mechanism
The setup invokes a shell or PowerShell command that pipes the remote installer into a shell or expression evaluator, then uses uv to create an environment and install the core.
AI rationale
The automatic install path executes a remote installer when uv is missing, creating a concrete but product-related remote execution risk. The inspected source does not establish a malicious payload or justify blocking publication.
Evidence
package.jsonscripts/postinstall.jsdist/install.mjs~/.hum
Network endpoints2
astral.sh/uv/install.ps1astral.sh/uv/install.sh
Decision evidence
public snapshotAI called this Suspicious at 85.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest runs a postinstall script automatically when the package is installed.
- The postinstall script invokes core setup when the installed core version differs.
- Core setup can run a shell command that downloads and executes an installer from astral.sh.
- Core setup also creates a Python environment and installs the package's core component.
Evidence against
- The setup code installs the stated Python environment and core component under the user's Hum directory.
- A later package fetch uses the same package name and disables npm lifecycle scripts.
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsFilesystemShell
HighEntropyStringsUrlStrings
NoLicense
Oversized source lightweight scan
Source & flagged code
5 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 unpkgbin/hum.jsView file
25const own = JSON.parse(fs.readFileSync(path.join(here, '..', 'package.json'), 'utf8')).version;
L26: const { chosenEntry } = await import(asUrl(path.join(here, '..', 'dist', 'install.mjs')));
L27: entry = chosenEntry(own) || entry;
Medium
Dynamic Require
Package source references dynamic require/import behavior.
bin/hum.jsView on unpkg · L25Findings
1 High6 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
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
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @metaphi-ai/hum@0.2.39.
See all versions of @metaphi-ai/hum for other recorded verdicts.
- Review the evidence and your use of @metaphi-ai/hum@0.2.39 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.