negotium@0.21.3
Install the Negotium multi-agent runtime and CLI with one package
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe install-time network and filesystem behavior is package-aligned tool setup with pinned versions and SHA-256 checks. The inspected agent integration locations do not show a confirmed attack, and the scanner hints alone do not establish credential redirection or command-output exfiltration.
Decision evidence
public snapshot- package.json runs two explicit postinstall installers for the package's browser and bash tools.
- Both installers fetch pinned release assets and verify SHA-256 before installing them under the Negotium state directory.
- The required agent-integration locations show paths, rollout handling, and scoped Codex environment setup; these excerpts do not establish an unconsented foreign agent-control write.
- The query runtime excerpt shows a normal bundled module import.
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.21.3.
See all versions of negotium for other recorded verdicts.
- Review the evidence and your use of negotium@0.21.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.