negotium@0.22.3
Install the Negotium multi-agent runtime and CLI with one package
AI Security Review
scanned 3d ago · by lpm-firewall-aiSource inspection found a postinstall binary setup with pinned project releases and SHA-256 checks, plus runtime behavior consistent with local agent and provider use. The reported credential redirect is not supported by the inspected provider configuration, which reads user vault keys for named providers.
Decision evidence
public snapshot- The postinstall hook runs two installers that fetch version-pinned project releases and check each binary against a SHA-256 value before writing it.
- Maestro provider keys are read from the user's vault for named providers and passed to the provider configuration; the inspected flow shows no fixed unofficial gateway.
- The inspected Codex server launch uses the local runtime and communicates over standard input and output.
- The inspected agent paths use the user's Codex home or the default home directory for authentication and scoped runtime configuration.
- Claude rollout helpers write or move session records within the user's Claude projects directory.
- The query runtime excerpt initializes a local SQLite adapter.
- Installation triggers a postinstall hook, and the runtime handles provider credentials and launches local agent processes; the inspected source shows these behaviors in product-related flows.
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/chunk-6c637pwe.jsView on unpkg · L7Findings
Affected versions and remediation
This report applies to negotium@0.22.3.
See all versions of negotium for other recorded verdicts.
- Review the evidence and your use of negotium@0.22.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.