negotium@0.2.24
Install the Negotium multi-agent runtime and CLI with one package
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package is not concretely malicious by source inspection, but its postinstall native-binary staging and agent shell/browser runtime warrant a warning. Fixed endpoints and digest verification materially reduce payload-substitution risk.
Decision evidence
public snapshot- package.json runs postinstall.
- install-browser-rs.mjs downloads a native browser binary.
- install-bash-rs.mjs downloads a native shell-service binary.
- The downloaded binaries are persisted under the Negotium state directory.
- Both installers require fixed SHA-256 digests before replacing a binary.
- Install scripts do not execute the downloaded binaries.
- Remote URLs are fixed GitHub release paths, not user-controlled.
- Runtime config only reads Codex global MCP config; no global config mutation was found.
- Shell/browser services use loopback URLs and capability tokens.
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.2.24.
See all versions of negotium for other recorded verdicts.
- Review the evidence and your use of negotium@0.2.24 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.