base44@0.1.18
Base44 CLI - Unified interface for managing Base44 applications
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe CLI has an active, default-on telemetry path that can transmit API request and response bodies on errors, creating a conditional data exposure risk. The inspected code does not establish intentional secret theft or unrelated-recipient exfiltration, so this warrants a warning rather than a block.
Decision evidence
public snapshot- The CLI sends telemetry to PostHog unless BASE44_DISABLE_TELEMETRY is set to "1".
- On API errors, telemetry properties include request and response bodies, which may contain sensitive data.
- The executable entrypoint runs the CLI; the manifest has no install lifecycle hooks.
- The inspected code reports errors and command context; it does not establish that secrets are deliberately collected.
- Telemetry is sent to the configured PostHog service, not an unrelated operator endpoint.
Source & flagged code
4 flaggedPackage source references dynamic require/import behavior.
dist/assets/backend-runtime/main.tsView on unpkg · L148Package contains source files above the normal full-analysis size ceiling.
dist/cli/index.jsView on unpkgFindings
Affected versions and remediation
This report applies to base44@0.1.18.
See all versions of base44 for other recorded verdicts.
- Review the evidence and your use of base44@0.1.18 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.