@velaro/cli@1.4.103
⚠ Under reviewVelaro Workspace v20 — command-line interface for managing bots, knowledge base ingestion, MCP API keys, search indexes, and ops health.
AI Security Review
scanned 13d ago · by lpm-firewall-aiStatic inspection found no confirmed attack in the flagged install, update, logging, or screenshot paths. The MCP key module imported by the CLI contains conflicting handler code that appears syntactically invalid, so the package’s actual runtime behavior cannot be fully resolved from this snapshot.
Decision evidence
public snapshot- The CLI entrypoint imports the MCP key command module, so that module is on startup’s import path.
- The MCP key handler opens an object assignment and then begins a second handler implementation with declarations inside it, leaving the source internally inconsistent and apparently unparsable.
- The install hook delegates to a script that imports banner text and writes it to a terminal or stderr.
- The update command runs a package installation only from its explicit command handler.
- The postinstall source shows banner output and no network request or file mutation.
- The screenshot helper invokes Python with a fixed script path and separate argument values.
Source & flagged code
10 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage manifest contains a dependency pinned to a remote tarball URL.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @velaro/cli@1.4.103.
See all versions of @velaro/cli for other recorded verdicts.
- Review the evidence and your use of @velaro/cli@1.4.103 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.