negotium@0.8.0
Install the Negotium multi-agent runtime and CLI with one package
AI Security Review
scanned 14d ago · by lpm-firewall-aiSource inspection found a postinstall download, but the installers use fixed releases and hash checks and place binaries in package state. The flagged session, secret, and agent integration paths showed package-aligned behavior; no concrete attack surface was established.
Decision evidence
public snapshot- package.json limits postinstall to two package helper installers.
- The installers fetch helper binaries; source inspection showed fixed releases, SHA-256 verification, and installation under the package’s state directory.
- The Claude-related paths handle session rollout files; the inspected code places or removes files for requested session operations.
- The local secret helper reads caller configuration or creates a random secret and stores it with restrictive permissions.
- Maestro API key overrides come from the user’s vault; the peer bridge accepts only loopback HTTP destinations.
- The required flagged files were inspected; their indicated locations show package runtime, session, or configuration behavior, not an attack.
Source & flagged code
10 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 · L9Findings
Affected versions and remediation
This report applies to negotium@0.8.0.
See all versions of negotium for other recorded verdicts.
- Review the evidence and your use of negotium@0.8.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.