negotium@0.5.15
Install the Negotium multi-agent runtime and CLI with one package
AI Security Review
scanned 2mo ago · by lpm-firewall-aiDirect inspection does not substantiate the scanner’s claims of credential redirection, foreign-package overwrite, or command-output exfiltration. The observed lifecycle downloader pins hashes and the inspected MCP network path is loopback-only.
Decision evidence
public snapshot- Postinstall only invokes two package-local binary installers.
- Each installer verifies a pinned SHA-256 before placing its downloaded binary.
- The alleged gateway path is restricted to loopback hosts and uses a caller-supplied environment URL/token.
- No fixed unofficial credential gateway or command-output exfiltration was found in the inspected MCP factory.
- No install-time mutation of Codex, Claude, or other foreign agent configuration was found.
- Runtime agent and MCP features are package-aligned, user-invoked functionality.
Source & flagged code
11 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.5.15.
See all versions of negotium for other recorded verdicts.
- Review the evidence and your use of negotium@0.5.15 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.