@velaro/cli@1.4.136
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 postinstall script only prints a banner, and the flagged command execution and credential flows are tied to explicit CLI operations. The startup updater uses the official npm registry and announces automatic updates with an opt-out; usage tracking sends only the action and CLI version to the configured Velaro API.
Decision evidence
public snapshot- The postinstall hook imports banner text and writes it to the terminal or stderr; it does not perform network or project-data collection.
- The background update check fetches the latest version from the official npm registry. Registry installs may update automatically, with a visible notice and a VELARO_NO_AUTO_UPDATE opt-out.
- Usage tracking sends only the CLI action and version, authenticated to the Velaro API base from the user's config.
- Screenshot capture is an explicitly invoked article subcommand that captures a staging page and updates the selected article.
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.136.
See all versions of @velaro/cli for other recorded verdicts.
- Review the evidence and your use of @velaro/cli@1.4.136 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.