registry / @velaro/cli / 1.4.67
@velaro/cli@1.4.67
Velaro Workspace v20 — command-line interface for managing bots, knowledge base ingestion, MCP API keys, search indexes, and ops health.
AI Security Review
scanned 27d ago · by lpm-firewall-aiSource inspection found a benign banner-only postinstall and user-invoked CLI operations for screenshots and updates. The scanner’s execution and exfiltration indicators were not substantiated by the inspected behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Package installation displays the banner; screenshot capture and package updating require their respective CLI actions.
Impact
The inspected behavior is consistent with the package’s CLI functions; no concrete attack surface was established.
Mechanism
The screenshot feature captures a selected Velaro page, polishes the image with a fixed script, and uploads it to the Velaro article API. The update command checks npm metadata and installs the named Velaro CLI package.
AI rationale
Source inspection found a benign banner-only postinstall and user-invoked CLI operations for screenshots and updates. The scanner’s execution and exfiltration indicators were not substantiated by the inspected behavior.
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The install hook imports and calls the first-run banner; it contains no install command, remote download, or broad configuration mutation.
- The screenshot helper requires an explicit app, route, and article ID, then sends the resulting image with a Velaro bearer token to the Velaro article upload endpoint.
- The screenshot helper invokes Python with a script path and argument array for image polishing.
- The update command fetches the latest package version from the npm registry and runs the package install only from its update handler.
Evidence against
- The package has a postinstall hook and uses child-process execution, but inspected code ties these to a banner and a fixed screenshot-polishing script.
- The scanner’s command-output exfiltration hint is not supported by the inspected update handler, which fetches npm version metadata and performs the named package update.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
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
1 Critical8 High5 Medium5 Low
CriticalPrevious Version Dangerous Deltalib/kb-screenshot.js
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/kb-screenshot.js#virtual:normalized:round1
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
Affected versions and remediation
This report applies to @velaro/cli@1.4.67.
See all versions of @velaro/cli for other recorded verdicts.
- Review the evidence and your use of @velaro/cli@1.4.67 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.