negotium@0.14.2
Install the Negotium multi-agent runtime and CLI with one package
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo concrete malicious behavior was established, but automatic native-binary installation and permission-bypassing agent orchestration create a real elevated-capability risk. This warrants a warning rather than a publication block.
Decision evidence
public snapshot- Its postinstall hook automatically runs two installers.
- The browser installer downloads, verifies, and installs an executable under the user's Negotium state directory.
- Runtime launches Claude with permission bypass enabled.
- Runtime writes synthetic session records into Claude's user directory.
- Cron prompt summaries can send a configured API-key request to DeepSeek or an environment-selected URL.
- Downloaded installer payloads are checked against hard-coded SHA-256 values before installation.
- The installer writes only to the package-owned .negotium state area.
- The DeepSeek call requires a supplied API key and uses the official endpoint by default.
- No source evidence shows secret harvesting, unsolicited external exfiltration, or install-time mutation of Codex or Claude configuration.
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 unpkgPackage source references child process execution.
dist/hosted-agent.jsView on unpkg · L9Findings
Affected versions and remediation
This report applies to negotium@0.14.2.
See all versions of negotium for other recorded verdicts.
- Review the evidence and your use of negotium@0.14.2 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.