@velaro/cli@1.4.137
Velaro Workspace v20 — command-line interface for managing bots, knowledge base ingestion, MCP API keys, search indexes, and ops health.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe CLI sends runtime usage telemetry after every successful wrapped command, and the inspected source provides no user-facing disclosure or opt-out. The event contains only the command action and version and goes to the configured Velaro API, so this is suspicious telemetry rather than evidence of data theft.
Decision evidence
public snapshot- After each successful wrapped command, the CLI sends an event containing the action name and CLI version to the configured API base’s `/ToolUsage/cli` endpoint.
- The tracking call uses the stored Velaro token for authorization; the inspected event body contains no command output or other free-form input.
- The postinstall script prints a version banner and does not send network requests.
- The `update` command runs the npm install command only when the user invokes `velaro update`.
- The screenshot flow is an explicit article subcommand and sends its image and article requests to the configured Velaro API base.
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.137.
See all versions of @velaro/cli for other recorded verdicts.
- Review the evidence and your use of @velaro/cli@1.4.137 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.