@vibiz/cli@0.2.2
The Vibiz Stack CLI and MCP server: website, database, sign-in, email and AI for a new business, from your terminal or your AI agent.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe credential-redirection and exfiltration indicators were not confirmed: Vibiz keys are sent to the configured Vibiz API. The login flow does send hostname and OS details to that service without an evident disclosure, so this is suspicious telemetry rather than a clean result.
Decision evidence
public snapshot- The explicit login flow sends the machine hostname, OS platform and release, and CLI version to the login service.
- Login uses the configured API URL, defaulting to the package’s own service; the request contains device metadata, not an API key.
- The automatic update check requests the CLI’s latest version from npm and caches the returned version.
- The manifest exposes a CLI executable and declares no install lifecycle scripts.
- The inspected API client sends its Vibiz key to the configured Vibiz API base URL; no credential redirect to an unrelated host was found.
Source & flagged code
6 flaggedPackage source references weak cryptographic algorithms.
dist/chunk-OKWUSSLA.jsView on unpkg · L48Findings
Affected versions and remediation
This report applies to @vibiz/cli@0.2.2.
See all versions of @vibiz/cli for other recorded verdicts.
- Review the evidence and your use of @vibiz/cli@0.2.2 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.