@velaro/cli@1.4.90
Velaro Workspace v20 — command-line interface for managing bots, knowledge base ingestion, MCP API keys, search indexes, and ops health.
AI Security Review
scanned 23d ago · by lpm-firewall-aiThe flagged behaviors are explained by the package's CLI functions and do not establish a concrete attack. The install hook only displays a banner, and the credential-related paths use Velaro authentication and API endpoints.
Decision evidence
public snapshot- The package's postinstall hook displays a version banner; it does not install packages, collect data, or make network requests.
- The screenshot utility is called from the article command with a selected app and route, and uploads the resulting image to the Velaro knowledge base.
- OAuth refresh sends the stored refresh token to the Velaro login endpoint; billing requests use the CLI's authenticated API client.
- The updater is an explicit CLI command that checks npm and installs a newer release of this same package.
- The optional spreadsheet dependency declares test and build scripts, with no install lifecycle script in its manifest.
- The package has a postinstall hook and runtime code uses network access and child-process execution, but inspected paths tie these behaviors to a banner or explicit CLI commands.
- The billing sync command defaults to a dry run and requires the user to pass --live to request a live sync.
Source & flagged code
9 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.90.
See all versions of @velaro/cli for other recorded verdicts.
- Review the evidence and your use of @velaro/cli@1.4.90 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.