@metaphi-ai/hum@0.2.62
Hum: a self-improving coding agent for your terminal.
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe lifecycle installer appears scoped to installing Hum’s own Python core. The runtime reporter’s configurable destination can receive a saved service token, so this warrants a warning for conditional credential exposure.
Decision evidence
public snapshot- The package postinstall hook runs scripts/postinstall.js, which calls installCore when its matching core is missing.
- The health reporter takes its destination from HUM_AUTH_URL or credentials.json auth_url, with https://hum.metaphi.ai as the fallback.
- The reporter reads credentials.json access_token and sends it as a bearer token with a POST to the health endpoint.
- Pending reports are sent automatically during interactive startup and after CLI commands.
- The install hook installs the matching hum-cli Python core; the inspected lifecycle path does not establish broad consumer-project mutation.
- The default health destination is the Hum service host.
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.62.
See all versions of @metaphi-ai/hum for other recorded verdicts.
- Review the evidence and your use of @metaphi-ai/hum@0.2.62 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.