base44@0.1.16
Base44 CLI - Unified interface for managing Base44 applications
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe manifest provides a user-invoked CLI entrypoint without an npm install lifecycle hook, and the inspected runtime and telemetry behavior are consistent with that purpose. Telemetry includes user-linked error context but targets the named PostHog service and has an environment-variable opt-out; no concrete malicious chain was found.
Decision evidence
public snapshot- package.json defines a CLI entrypoint and has no preinstall, install, or postinstall hook; its remote tarball dependency is @deno/loader.
- bin/run.js invokes the bundled CLI when the user runs the command.
- CLI telemetry is disabled by BASE44_DISABLE_TELEMETRY=1 and targets us.i.posthog.com.
- Error telemetry may use the authenticated user's email as its distinct ID.
- The backend wrapper dynamically imports the function path supplied through FUNCTION_PATH.
- Inspected behavior is consistent with an application-management CLI: telemetry is sent to a named analytics service and local runtime imports a caller-selected function.
- No inspected source showed an install-time attack, credential forwarding to an unrelated recipient, or a malicious payload chain.
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.16.
See all versions of base44 for other recorded verdicts.
- Review the evidence and your use of base44@0.1.16 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.