cyberneurova-cli@0.20.0
The CyberNeurova terminal AI coding agent
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe flagged credential flow is consistent with provider-specific configuration, including a CyberNeurova key sent to the vendor's API. The package has no install lifecycle hook, and the inspected download-and-run command points to the vendor's own installer.
Decision evidence
public snapshot- The manifest exposes dist/main.mjs as the CLI entry point and declares no install lifecycle hook.
- Provider configuration maps Anthropic, OpenAI, CyberNeurova and Google keys to their corresponding provider types.
- The CyberNeurova API-key provider uses the package vendor's API endpoint.
- The native updater command references the vendor's own install script.
- The bundled source includes cloud metadata addresses, but the inspected references are in bundled cloud SDK code; no automatic metadata collection flow was identified.
- A download-and-run shell command is constructed for the vendor's install script, but no install-time invocation was identified.
Source & flagged code
11 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/main.mjsView on unpkg · L5Manifest-reachable source sends a prompted API credential to a fixed unofficial gateway and persists the redirection.
dist/main.mjsView on unpkgFindings
Affected versions and remediation
This report applies to cyberneurova-cli@0.20.0.
See all versions of cyberneurova-cli for other recorded verdicts.
- Review the evidence and your use of cyberneurova-cli@0.20.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.