registry / @velaro/cli / 1.4.112
@velaro/cli@1.4.112
Velaro Workspace v20 — command-line interface for managing bots, knowledge base ingestion, MCP API keys, search indexes, and ops health.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe install hook only prints a banner. Runtime update and KB upload behavior is tied to the CLI’s stated purpose; the self-update is announced and has an environment opt-out, and no unrelated credential destination or concealed payload was found.
Static reason
One or more suspicious static signals were detected.
Trigger
Installation prints a banner; the CLI checks for updates when invoked. Screenshot upload and article changes require an explicit command.
Impact
No unrelated credential transfer or hidden install-time activity was found. The updater can replace this CLI with a newer release unless disabled.
Mechanism
The updater checks the package’s npm registry entry and may install a newer @velaro/cli release. Screenshot tooling uploads an image to the configured Velaro API and updates the selected article.
AI rationale
The install hook only prints a banner. Runtime update and KB upload behavior is tied to the CLI’s stated purpose; the self-update is announced and has an environment opt-out, and no unrelated credential destination or concealed payload was found.
Evidence
~/.velaro/config.jsontemporary KB screenshot files
Network endpoints2
registry.npmjs.org/@velaro/cli/latesthelp.velaro.com/api/kb/articles/upload-image
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 the package banner to a terminal or stderr; it makes no network request.
- The background update check contacts the npm registry for this package and caches the result; automatic updates are announced and can be disabled with VELARO_NO_AUTO_UPDATE=1.
- The update command is an explicit CLI action and installs @velaro/cli from npm.
- Screenshot capture and KB article upload require an explicit article screenshot command and use the configured Velaro API with the Velaro token.
Evidence against
- Registry installs can automatically run npm install -g @velaro/cli@latest after an update check finds a newer version, unless disabled by environment or CI.
- The explicit screenshot command uploads an image and updates the selected KB article.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStrings
Source & flagged code
9 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 High5 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
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumRemote Tarball Dependency
Affected versions and remediation
This report applies to @velaro/cli@1.4.112.
See all versions of @velaro/cli for other recorded verdicts.
- Review the evidence and your use of @velaro/cli@1.4.112 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.