negotium@0.16.0
Install the Negotium multi-agent runtime and CLI with one package
AI Security Review
scanned 1mo ago · by lpm-firewall-aiNo source evidence establishes credential theft, agent-control hijacking, destructive behavior, or a self-dependency chain. Automatic download of opaque executables during postinstall remains a real supply-chain risk that warrants a warning.
Decision evidence
public snapshot- The npm postinstall hook automatically runs two native-binary installers.
- Both installers download opaque platform executables, make them executable, and place them in the user's Negotium state directory.
- The runtime later starts the downloaded bash executable as a child process.
- The installers pin SHA-256 hashes and reject a downloaded file whose hash differs.
- The install hook writes only under the package-specific Negotium state directory; no foreign agent configuration write was found.
- The DeepSeek request uses an explicit configured key and its documented default endpoint; no fixed unofficial credential gateway was found.
Source & flagged code
7 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 dynamic require/import behavior.
dist/hosted-agent.jsView on unpkg · L213Findings
Affected versions and remediation
This report applies to negotium@0.16.0.
See all versions of negotium for other recorded verdicts.
- Review the evidence and your use of negotium@0.16.0 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.