negotium@0.2.19
Install the Negotium multi-agent runtime and CLI with one package
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe lifecycle downloads are explicit, hash-pinned companion binaries for documented browser and shell functionality. Source inspection found no credential harvesting, covert external endpoint, or install-time mutation of a foreign AI-agent control surface.
Decision evidence
public snapshot- package.json runs postinstall downloaders
- install-browser-rs.mjs fetches a native binary
- install-bash-rs.mjs fetches a native binary
- Both installers pin SHA-256 and verify before install
- Downloads only write package-owned ~/.negotium binaries
- No lifecycle AI-agent config mutation found
- Runtime agent integrations are activated by CLI/runtime use
- Peer forwarding is restricted to authenticated loopback URLs
- Vault HTTP requires HTTPS and explicit credential placeholders
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 · L8Findings
Affected versions and remediation
This report applies to negotium@0.2.19.
See all versions of negotium for other recorded verdicts.
- Review the evidence and your use of negotium@0.2.19 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.