negotium@0.2.17
Install the Negotium multi-agent runtime and CLI with one package
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe lifecycle behavior is a checksum-verified install of documented, package-owned binaries, not a foreign AI-agent control-surface mutation. Runtime shell and HTTPS capabilities are explicit MCP features with credential-bound/redacted handling; no concrete malicious chain was found.
Decision evidence
public snapshot- package.json defines postinstall.
- install-browser-rs.mjs downloads and installs a native executable.
- install-bash-rs.mjs downloads and installs a native executable.
- dist/runtime/src/mcp/vault-run.ts can run user-requested credential-bearing shell commands.
- Install downloads are pinned to GitHub release URLs and SHA-256 verified.
- Installers only write Negotium-owned ~/.negotium binaries and can be skipped by env flags.
- No source evidence of credential harvesting or hard-coded exfiltration endpoint.
- Vault HTTP/shell functions require explicit MCP inputs and redact returned secret material.
- Agent-session writes are runtime features, not lifecycle execution.
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.17.
See all versions of negotium for other recorded verdicts.
- Review the evidence and your use of negotium@0.2.17 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.