negotium@0.5.6
Install the Negotium multi-agent runtime and CLI with one package
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe scanner's claimed fixed credential gateway and foreign-package overwrite were not confirmed in source. The confirmed runtime manipulation of Codex session/control state is a dangerous, user-invoked agent capability and merits a warning rather than a malware block.
Decision evidence
public snapshot- Runtime creates synthetic Codex session rollouts and sets their sandbox policy to danger-full-access.
- A user-invoked Codex turn writes a Negotium model catalog into the user's Codex state directory.
- postinstall downloads native browser and shell helper binaries into ~/.negotium.
- The Codex-state writes are reached during provider execution, not npm installation.
- The downloaded helpers use fixed GitHub release locations and hard-coded SHA-256 verification.
- Inspected MCP factory code exposes localhost endpoints; no fixed credential-redirection or command-output exfiltration endpoint was found.
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.6.
See all versions of negotium for other recorded verdicts.
- Review the evidence and your use of negotium@0.5.6 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.