negotium@0.22.2
Install the Negotium multi-agent runtime and CLI with one package
AI Security Review
scanned 3d ago · by lpm-firewall-aiSource inspection found a postinstall binary setup that uses pinned release assets and checksum validation, plus local agent authentication and session handling. The scanner’s credential-redirection signal corresponds to local Codex auth-path resolution; no credential transfer or other concrete attack was identified.
Decision evidence
public snapshot- package.json activates two binary installers; each fetches a fixed release asset and checks its SHA-256 before installation.
- Both installers place binaries under the Negotium state directory.
- The flagged Codex auth helper resolves a local auth-file path; the auth check tests whether that file exists.
- The flagged agent and registry code writes session rollout files to the user’s Claude projects directory.
- The flagged query runtime initializes a standard stderr logger; the remaining flagged bundle locations contain local auth-path resolution or agent runtime setup.
- The postinstall downloads executable binaries, but the inspected installer code pins release versions and rejects checksum mismatches.
- The reviewed credential-related code does not show a transfer to an unofficial gateway or other recipient.
Source & flagged code
8 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 · L50Findings
Affected versions and remediation
This report applies to negotium@0.22.2.
See all versions of negotium for other recorded verdicts.
- Review the evidence and your use of negotium@0.22.2 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.