base44@0.1.24
Base44 CLI - Unified interface for managing Base44 applications
AI Security Review
scanned 27d ago · by lpm-firewall-aiSource inspection found a CLI entrypoint and user-function runtime, with no install lifecycle hook or concrete attack behavior. The remote tarball dependency and scanner signals alone do not establish malicious activity.
Decision evidence
public snapshot- package.json identifies base44 as a CLI and exposes bin/run.js as its command.
- bin/run.js imports and starts the CLI entrypoint.
- The backend runtime dynamically imports the user-selected function and provides a Base44 secrets bridge backed by the local environment.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- The inspected runtime behavior supports running user functions; no credential exfiltration or unrelated recipient was established.
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.24.
See all versions of base44 for other recorded verdicts.
- Review the evidence and your use of base44@0.1.24 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.