@velaro/cli@1.4.153
Velaro Workspace v20 — command-line interface for managing bots, knowledge base ingestion, MCP API keys, search indexes, and ops health.
AI Security Review
scanned 20h ago · by lpm-firewall-aiThe package's default startup behavior can update and execute a newer CLI release without an explicit update request, so this is a suspicious automatic action rather than a confirmed attack. The install hook only prints a banner, and the separate update command is user-invoked.
Decision evidence
public snapshot- The CLI starts the update check during startup.
- The checker fetches the latest version from registry.npmjs.org once per day and caches the result.
- When a registry install has a newer version, the CLI starts a detached global npm install of @velaro/cli@latest unless VELARO_NO_AUTO_UPDATE or CI is set.
- The postinstall script prints a version banner to the terminal.
- The automatic update is limited to the package's own latest release from the npm registry and prints an update notice.
- The manifest's postinstall hook only runs the banner script.
- The separate velaro update command runs its npm install only when explicitly invoked.
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.153.
See all versions of @velaro/cli for other recorded verdicts.
- Review the evidence and your use of @velaro/cli@1.4.153 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.