@velaro/cli@1.4.130
Velaro Workspace v20 — command-line interface for managing bots, knowledge base ingestion, MCP API keys, search indexes, and ops health.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe install hook only prints a banner, and update checks use the official npm registry to check and optionally install this CLI's own update. A usage-tracking request exists in source, but its credential gate does not match the normal config structure, so it is skipped for standard configurations.
Decision evidence
public snapshot- The postinstall hook prints a version banner to the terminal or stderr.
- The update checker queries the official npm registry for this package and caches version metadata.
- The tracker requires root-level credentials; normal config migration stores credentials under `envs`, so the tracking request is skipped for standard configs.
- The package declares a postinstall hook.
- The CLI can install its own update in the background when a newer version is available, unless disabled with `VELARO_NO_AUTO_UPDATE=1` or running in CI.
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.130.
See all versions of @velaro/cli for other recorded verdicts.
- Review the evidence and your use of @velaro/cli@1.4.130 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.