@metaphi-ai/hum@0.2.20
Hum: a self-improving coding agent for your terminal.
AI Security Review
scanned 14d ago · by lpm-firewall-aiSource inspection confirms an automatic postinstall setup path, including a fallback that executes Astral’s `uv` installer, but the observed operations install Hum’s matching core and stage the same package with scripts disabled. The scanner’s browser credential collection hint was not substantiated by the inspected source, so the package is marked clean.
Decision evidence
public snapshot- The manifest’s postinstall hook runs the package’s own setup script.
- The setup script installs the core only when the current version is not already installed.
- The installer uses Astral’s `uv` installer as a fallback and defaults to installing the matching `hum-cli` version.
- The installer stages the same Hum package version with lifecycle scripts disabled before moving it into its version directory.
- The CLI only completes core installation for npm layouts when an install is needed.
- The postinstall hook can execute a downloaded shell installer automatically when `uv` is unavailable.
Source & flagged code
9 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.2.20.
See all versions of @metaphi-ai/hum for other recorded verdicts.
- Review the evidence and your use of @metaphi-ai/hum@0.2.20 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.