negotium@0.21.0
Install the Negotium multi-agent runtime and CLI with one package
AI Security Review
scanned 14d ago · by lpm-firewall-aiInspected sources show a postinstall hook for package-owned runtime binaries and no confirmed malicious data flow. The scanner's gateway and command-output signals were not substantiated by the inspected source.
Decision evidence
public snapshot- package.json sets a postinstall hook to run the two package-owned binary installers.
- The browser installer downloads a fixed release asset to the package's state directory and checks its SHA-256 digest before accepting it.
- The bash installer likewise uses fixed release assets, digest checks, and a package state directory.
- The inspected agent configuration locations show auth path selection, session-file writing, and per-run Codex environment setup; they do not establish an unconsented install-time control-surface mutation.
- DEEPSEEK_API_KEY is read from the vault for model configuration; the inspected search found no api.deepseek endpoint literal.
- No inspected source established credential forwarding to an unofficial gateway or command-output exfiltration.
- The postinstall hook invokes package-aligned binary setup rather than modifying a foreign AI-agent configuration surface.
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 · L50Findings
Affected versions and remediation
This report applies to negotium@0.21.0.
See all versions of negotium for other recorded verdicts.
- Review the evidence and your use of negotium@0.21.0 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.