negotium@0.19.1
Install the Negotium multi-agent runtime and CLI with one package
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe inspected install-time network behavior is limited to downloading hash-checked, package-related binaries. Flagged credential and agent-integration locations show auth-path resolution, isolated Codex home selection, or session data handling; they do not establish credential forwarding or an unconsented control-surface change.
Decision evidence
public snapshot- package.json defines a postinstall that runs two helper installers.
- The installers fetch fixed release assets from the package’s GitHub organization, verify SHA-256 hashes, and place binaries in the Negotium state directory.
- The flagged Codex auth paths locate auth.json; the inspected agent code uses an isolated CODEX_HOME when needed, and the other flagged locations concern agent session data or path setup.
- The inspected runtime entry files show no evidence of credential forwarding, broad agent-control mutation, or another concrete attack.
Source & flagged code
7 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 dynamic require/import behavior.
dist/hosted-agent.jsView on unpkg · L679Findings
Affected versions and remediation
This report applies to negotium@0.19.1.
See all versions of negotium for other recorded verdicts.
- Review the evidence and your use of negotium@0.19.1 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.