negotium@0.5.14
Install the Negotium multi-agent runtime and CLI with one package
AI Security Review
scanned 2mo ago · by lpm-firewall-aiDirect inspection found broad but package-aligned agent/runtime functionality, not the claimed credential redirection or foreign-package overwrite. The install-time downloads are pinned and hash-verified, and observed credential handling is local or tied to an explicitly configured model request.
Decision evidence
public snapshot- postinstall only downloads two version-pinned GitHub release binaries after SHA-256 verification.
- Installers write only under NEGOTIUM_STATE_DIR or ~/.negotium and can be skipped with package-specific environment flags.
- No fixed unofficial credential gateway or credential-exfiltration URL was found in inspected code.
- Codex auth is copied only to a temporary isolated home to invoke the installed Codex CLI for a model cache; the temporary directory is removed.
- The Cron API request uses an explicit environment credential and the official DeepSeek endpoint; its URL is overrideable.
- Peer forwarding accepts only loopback HTTP bridge URLs.
Source & flagged code
11 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.5.14.
See all versions of negotium for other recorded verdicts.
- Review the evidence and your use of negotium@0.5.14 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.