negotium@0.4.3
Install the Negotium multi-agent runtime and CLI with one package
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package contains a concrete runtime mechanism to create privileged-looking foreign Codex session state, warranting a warning. Its postinstall hook is limited to checksum-verified package-aligned binary downloads and does not modify AI-agent control surfaces.
Decision evidence
public snapshot- Runtime rollout builder injects `danger-full-access` and disables approvals.
- It writes synthetic Codex rollout files when its rollout operation is invoked.
- Postinstall downloads checksum-pinned native helper binaries.
- No install hook writes Codex, Claude, or other agent-control files.
- No fixed credential-exfiltration gateway was found in inspected source.
- The binary downloads are pinned to SHA-256 values and stored under Negotium state.
Source & flagged code
10 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/chunk-ef4y7rz2.jsView on unpkg · L23Findings
Affected versions and remediation
This report applies to negotium@0.4.3.
See all versions of negotium for other recorded verdicts.
- Review the evidence and your use of negotium@0.4.3 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.