cyberneurova-cli@0.20.3
The CyberNeurova terminal AI coding agent
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe credential flow prompts for a key, verifies it with the selected provider, and stores the resulting configuration. The shell-based update path belongs to the CLI’s updater and uses the package’s official host; no malicious behavior was established.
Decision evidence
public snapshot- The manifest exposes the bundled CLI as its executable and has no install, preinstall, or postinstall hook.
- The API-key setup asks the user to enter a key, verifies it for the selected provider, then saves provider configuration; CyberNeurova’s configured API endpoint is api.cyberneurova.ai.
- The built-in updater uses the package’s official cyberneurova.ai installer and only starts background installation when auto-install is enabled and the install source supports it.
- The CLI includes shell execution and a download-and-run installer path for its native-platform updater.
- The CLI stores provider configuration, including API keys, in ~/.cyberneurova/config.toml.
Source & flagged code
11 flaggedPackage source references child process execution.
dist-web/assets/index-CxRV4At0.jsView on unpkg · L152Package source references dynamic require/import behavior.
dist-web/assets/codeql-DsOJ9woJ.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to cyberneurova-cli@0.20.3.
See all versions of cyberneurova-cli for other recorded verdicts.
- Review the evidence and your use of cyberneurova-cli@0.20.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.