negotium@0.17.0
Install the Negotium multi-agent runtime and CLI with one package
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe source confirms that user-vault provider keys are forwarded to the Maestro SDK, but does not establish the destination or prove theft. This leaves a conditional credential exposure risk that merits a warning rather than a block.
Decision evidence
public snapshot- The Maestro provider reads DeepSeek, Moonshot, and GLM keys from the user vault and passes them as API key overrides to the Maestro SDK; the package source does not show the SDK’s destination.
- The package has a postinstall hook, but its browser binary installer downloads a version-pinned release and checks its SHA-256 before installation.
- The keys are supplied to the package’s Maestro provider as credentials for its agent service; no credential theft or unrelated recipient is established by the inspected package source.
- The postinstall browser installer uses a fixed release URL and verifies the binary checksum before saving it under the Negotium state directory.
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.17.0.
See all versions of negotium for other recorded verdicts.
- Review the evidence and your use of negotium@0.17.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.