negotium@0.6.3
Install the Negotium multi-agent runtime and CLI with one package
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe source inspection supports package-aligned installation and runtime behavior. The flagged auth-file locations resolve paths but do not show credentials being sent; no concrete malicious behavior was established.
Decision evidence
public snapshot- The postinstall hook invokes two installer scripts for package-related browser and bash tools.
- Both installers use fixed GitHub release URLs and verify downloaded binaries against hard-coded SHA-256 hashes before replacing files under the Negotium state directory.
- The flagged Codex auth-file helpers only resolve a configurable auth-file path; these excerpts show no credential read or transmission.
- The registry code copies a Claude session file as part of its session-fork operation.
- The browser runtime binds its service to loopback, while runtime-helpers exports package utility functions.
- The package manifest identifies a CLI entrypoint and documents Negotium as a runtime and CLI package.
- The inspected source excerpts do not establish credential exfiltration, reviewer manipulation, or unconsented broad agent configuration changes.
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.6.3.
See all versions of negotium for other recorded verdicts.
- Review the evidence and your use of negotium@0.6.3 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.