registry / @velaro/cli / 1.4.127
@velaro/cli@1.4.127
Velaro Workspace v20 — command-line interface for managing bots, knowledge base ingestion, MCP API keys, search indexes, and ops health.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe postinstall script only prints a banner and does not contact the network. The flagged process execution is confined to the explicit updater command, and the reviewed credential flows support Velaro CLI functions.
Static reason
One or more suspicious static signals were detected.
Trigger
The banner runs at install; other network and process actions are triggered by explicit CLI commands or successful command completion.
Impact
No unauthorized credential transfer, install-time contact, or automatic destructive behavior was identified.
Mechanism
The updater checks the npm registry before installing the CLI; the screenshot workflow uses staging credentials; usage tracking sends an action and version to the configured Velaro API.
AI rationale
The postinstall script only prints a banner and does not contact the network. The flagged process execution is confined to the explicit updater command, and the reviewed credential flows support Velaro CLI functions.
Evidence
/dev/tty~/.velaro/config.json
Network endpoints3
registry.npmjs.org/@velaro/cli/latest${vaultName}.vault.azure.net${creds.apiBase}/ToolUsage/cli
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook only renders and writes a version banner to the terminal.
- The updater fetches the latest version and runs npm install only from the explicit update command.
- The screenshot helper retrieves staging credentials for its documented screenshot workflow.
- Usage tracking sends the action and CLI version to the configured Velaro API after a command succeeds.
- API requests use credentials from the Velaro CLI login configuration.
Evidence against
- The package declares a postinstall hook, but its source contains no network request or credential access.
- The source includes process execution, but the npm install invocation is part of the explicit updater command.
- Credential access in the screenshot helper is part of a documented staging workflow, not an import-time action.
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsFilesystemNetworkShell
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.127.
See all versions of @velaro/cli for other recorded verdicts.
- Review the evidence and your use of @velaro/cli@1.4.127 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.