negotium@0.2.30
Install the Negotium multi-agent runtime and CLI with one package
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe lifecycle scripts are transparent, checksum-verify fixed package-aligned releases, and write only Negotium-owned state. Source inspection found no concrete malicious chain, credential exfiltration, or unconsented foreign AI-agent control-surface mutation.
Decision evidence
public snapshot- package.json runs two postinstall scripts.
- Install scripts download native tool binaries to ~/.negotium/binaries.
- Both download URLs and SHA-256 hashes are hard-coded and verified.
- Downloads are package-aligned GitHub releases and can be skipped via NEGOTIUM_SKIP_* env vars.
- Install failures only disable optional tools and exit successfully.
- Runtime source uses per-turn Codex MCP overrides and states global config.toml remains untouched.
- Credential paths are checked or copied into isolated temporary homes; no exfiltration path was found.
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.30.
See all versions of negotium for other recorded verdicts.
- Review the evidence and your use of negotium@0.2.30 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.