negotium@0.16.5
⚠ Under reviewInstall the Negotium multi-agent runtime and CLI with one package
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe package source confirms vault credentials are supplied to an SDK, but does not establish the effective recipient or destination restrictions. This unresolved credential flow warrants manual review; the inspected Codex auth-path helper alone does not show credential transmission.
Decision evidence
public snapshot- The flagged `mcp-factories.js` location resolves the Codex `auth.json` path under `CODEX_HOME` or `.codex`; that excerpt does not show a write or transmission.
- The Maestro provider loads DeepSeek, Moonshot, and GLM keys from the user vault when a user ID is present.
- The inspected provider code passes those keys as API key overrides to `maestro-agent-sdk`; the SDK’s actual destination is not established by the inspected source.
- The package’s `postinstall` invokes two named helper installers; the inspected browser installer uses a versioned GitHub release URL and pinned SHA-256 values.
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.16.5.
See all versions of negotium for other recorded verdicts.
- Review the evidence and your use of negotium@0.16.5 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.