base44@0.1.25
Base44 CLI - Unified interface for managing Base44 applications
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe inspected source supports a user-invoked Base44 CLI, with no install lifecycle hook in package.json and no concrete malicious behavior established. The scanner’s dynamic import and network hints correspond to function loading and telemetry; they do not independently establish an attack.
Static reason
One or more suspicious static signals were detected.
Trigger
A user invokes the `base44` command or runs a function through the CLI.
Impact
No confirmed harmful effect or attack surface was identified.
Mechanism
The launcher calls the CLI entrypoint; the backend runtime dynamically imports FUNCTION_PATH. No malicious behavior was established from these actions.
AI rationale
The inspected source supports a user-invoked Base44 CLI, with no install lifecycle hook in package.json and no concrete malicious behavior established. The scanner’s dynamic import and network hints correspond to function loading and telemetry; they do not independently establish an attack.
Evidence
package.jsonbin/run.jsdist/assets/backend-runtime/main.ts
Decision evidence
public snapshotAI called this Clean at 87.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json identifies the package as the Base44 application CLI and declares no install lifecycle hooks.
- bin/run.js launches the bundled CLI when the user invokes the `base44` command.
- The runtime dynamically imports the function path supplied through FUNCTION_PATH to serve the user’s function.
- Telemetry is disabled when the telemetry opt-out environment variable is set to `1`.
- The manifest’s remote tarball dependency is @deno/loader; no source evidence inspected connects it to malicious behavior.
Evidence against
- The CLI includes telemetry enabled by default and sends to PostHog; inspected code shows an opt-out and no evidence of credential forwarding to that endpoint.
- The scanner’s dynamic import finding is part of the function-serving runtime, where it loads the user-selected function.
Behavioral surface
DynamicRequireEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
4 flaggeddist/assets/backend-runtime/main.tsView file
148try {
L149: functionModule = await import(functionPath);
L150: } catch (error) {
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/assets/backend-runtime/main.tsView on unpkg · L148dist/cli/index.jsView file
•path = dist/cli/index.js
kind = oversized_source_file
sizeBytes = 10874130
magicHex = [redacted]
Medium
Oversized Source File
Package contains source files above the normal full-analysis size ceiling.
dist/cli/index.jsView on unpkgpackage.jsonView file
•Remote tarball dependency specs: @deno/loader@https://npm.jsr.io/~/11/@jsr/deno__loader/0.5.0.tgz
Findings
6 Medium6 Low
MediumDynamic Requiredist/assets/backend-runtime/main.ts
MediumNetwork
MediumEnvironment Vars
MediumOversized Source Filedist/cli/index.js
MediumStructural Risk Force Deep Review
MediumRemote Tarball Dependencypackage.json
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowTelemetry
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to base44@0.1.25.
See all versions of base44 for other recorded verdicts.
- Review the evidence and your use of base44@0.1.25 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.