@velaro/cli@1.4.144
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 CLI commands trigger usage reports to the configured Velaro API, and the inspected path shows no user-facing disclosure or opt-out. The report contains the command name and version, so this is warning-level telemetry rather than data exfiltration.
Static reason
One or more suspicious static signals were detected.
Trigger
After a command wrapped by runCommand succeeds, provided the local configuration contains a Velaro token and API base.
Impact
The service can observe which CLI commands are used. The event does not include command arguments in the inspected implementation.
Mechanism
The CLI posts the action name and CLI version to {apiBase}/ToolUsage/cli with the stored Velaro bearer token. No opt-out was found in the inspected tracking code.
AI rationale
Successful CLI commands trigger usage reports to the configured Velaro API, and the inspected path shows no user-facing disclosure or opt-out. The report contains the command name and version, so this is warning-level telemetry rather than data exfiltration.
Evidence
lib/run.jslib/track.js
Network endpoints1
{creds.apiBase}/ToolUsage/cli
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- After each successful command handled by runCommand, the CLI sends the command name to track().
- track() posts the command name and CLI version to the configured API base, authenticated with the stored Velaro token; the inspected code has no opt-out.
- The postinstall hook prints a version banner and does not make a network request.
- The update command checks npm when the user invokes the update command.
Evidence against
- The usage event contains the action and CLI version, not command arguments or other environment values.
- The tracking destination is the configured API base and the bearer token is sent to that same base.
- The screenshot flow requires explicit app, route, and article ID inputs.
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
Source & flagged code
10 flaggedpackage.jsonView file
•scripts.postinstall = node scripts/postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkg•Remote tarball dependency specs: xlsx@https://cdn.sheetjs.com/xlsx-0.20.3/xlsx-0.20.3.tgz
Medium
Remote Tarball Dependency
Package manifest contains a dependency pinned to a remote tarball URL.
package.jsonView on unpkglib/kb-screenshot.jsView file
Findings
8 High6 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processlib/kb-screenshot.js
HighShell
HighSame File Env Network Executionlib/kb-screenshot.js
HighCommand Output Exfiltrationlib/commands/update.js
HighTrigger Reachable Command Output Exfiltrationlib/commands/update.js
HighRuntime Package Installlib/commands/update.js
HighSemantic Analysis Limitedlib/deploy-state.js#virtual:normalized:round1
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requirelib/track.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
Affected versions and remediation
This report applies to @velaro/cli@1.4.144.
See all versions of @velaro/cli for other recorded verdicts.
- Review the evidence and your use of @velaro/cli@1.4.144 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.