negotium@0.18.0
Install the Negotium multi-agent runtime and CLI with one package
AI Security Review
scanned 14d ago · by lpm-firewall-aiInspected source shows the postinstall downloaders verify pinned release binaries before installation. Vault API keys are passed to the package’s Maestro provider, but the inspected code does not establish an unrestricted credential destination or a concrete attack; the scanner signals alone do not support a warning or block.
Decision evidence
public snapshot- package.json exposes agent runtime modules; the inspected target locations mostly contain path handling and rollout-file operations, not foreign agent configuration changes.
- The postinstall scripts download version-pinned binaries from the project’s GitHub releases and verify their SHA-256 before installation under the Negotium state directory.
- The inspected API-key override code reads DeepSeek, Moonshot, and GLM keys from the user vault and passes them to the Maestro provider; no unrestricted recipient or actual network send was established in inspected source.
- The package has a postinstall hook that runs two binary installer scripts.
- Vault API keys are forwarded to the Maestro provider, but inspected source does not establish an unrestricted or unrelated destination.
Source & flagged code
7 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 dynamic require/import behavior.
dist/hosted-agent.jsView on unpkg · L212Findings
Affected versions and remediation
This report applies to negotium@0.18.0.
See all versions of negotium for other recorded verdicts.
- Review the evidence and your use of negotium@0.18.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.