@velaro/cli@1.4.141
Velaro Workspace v20 — command-line interface for managing bots, knowledge base ingestion, MCP API keys, search indexes, and ops health.
AI Security Review
scanned 4d ago · by lpm-firewall-aiSuccessful commands automatically trigger runtime usage telemetry, and the inspected source provides no opt-out or user-facing disclosure. The destination is the configured Velaro API and the payload is limited to the command action and CLI version, so this warrants a warning rather than a block.
Decision evidence
public snapshot- Successful commands handled by runCommand schedule usage tracking.
- Tracking sends the command action and CLI version to the configured Velaro API using the stored Velaro token.
- The install hook prints a version banner and does not show network or data collection behavior.
- The tracking request goes to the configured Velaro API, not an unrelated collector.
- The inspected tracking payload contains command action and CLI version, not credentials or command arguments.
- The postinstall script only writes a banner to the terminal or stderr.
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.141.
See all versions of @velaro/cli for other recorded verdicts.
- Review the evidence and your use of @velaro/cli@1.4.141 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.