negotium@0.6.17
Install the Negotium multi-agent runtime and CLI with one package
AI Security Review
scanned 14d ago · by lpm-firewall-aiSource inspection found a package-aligned postinstall that installs hash-verified helper binaries and no concrete malicious behavior. The scanner hints about agent integration point to ordinary path resolution, rollout handling, and localhost browser operations in the inspected excerpts.
Decision evidence
public snapshot- package.json exposes package-owned CLI and library entrypoints.
- The postinstall hook invokes two package-owned binary installers; each downloads from a fixed GitHub release and verifies the binary against a pinned SHA-256 before installation.
- Flagged agent integration locations resolve Codex auth paths, format user turns, write Claude rollout data, or probe a localhost browser service; inspected excerpts show no foreign agent configuration mutation or credential forwarding.
- The inspected source shows ordinary package functionality and no concrete attack behavior.
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/hosted-agent.jsView on unpkg · L9Findings
Affected versions and remediation
This report applies to negotium@0.6.17.
See all versions of negotium for other recorded verdicts.
- Review the evidence and your use of negotium@0.6.17 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.