runlot@0.1.0-rc.162
⚠ Under reviewrunlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 13d ago · by lpm-firewall-aiStatic inspection did not confirm malicious behavior. The required PGlite dependency and a bundled runtime executable used by local development remain unverified, so the package cannot be cleared as clean.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user starts local development with the PGlite backend or a Feather runtime.
Impact
The available source does not establish how these components handle data or secrets, so their behavior remains unverified.
Mechanism
The CLI dynamically loads PGlite or starts the selected development runtime, passing project secrets in its environment; the runtime executable's behavior could not be inspected.
AI rationale
Static inspection did not confirm malicious behavior. The required PGlite dependency and a bundled runtime executable used by local development remain unverified, so the package cannot be cleared as clean.
Evidence
dist/index.jsbin/linux-x64/runlot-dev-runtime.lpm-inspection-Bzs58Y/0-98ed4633eb93.txtpackage.json
Decision evidence
public snapshotAI called this Manual Review at 82.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest publishes dist/index.js and declares @electric-sql/pglite 0.4.3 as a required dependency.
- The local database implementation dynamically imports PGlite when opening that database.
- The CLI can select a bundled development runtime and launches it with project secrets in its environment.
- The trusted offline analysis identifies the Linux runtime as an ELF executable but cannot inspect its behavior.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
13 flaggeddist/index.jsView file
43// ../../packages/api/src/index.ts
L44: function base64urlJson(v) {
L45: const bytes = new TextEncoder().encode(JSON.stringify(v));
...
L50: function gitQuery(ref, path) {
L51: const q = new URLSearchParams();
L52: if (ref !== "") q.set("ref", ref);
...
L109: async request(method, path, init) {
L110: const res = await fetch(new URL(path, this.opts.baseUrl), {
L111: ...init,
...
L1144: * hostname (the original request went there), and the server derives the org
L1145: * and project names from it. Doing `location.replace` with the `redirect` that
L1146: * comes back is the caller's job.
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L433553});
L3554: readFromStdout(stdout);
L3555: afterClose(null);
...
L3563: let worker = new worker_threads2.Worker(__filename, {
L3564: workerData: { workerPort, defaultWD, esbuildVersion: "0.24.2" },
L3565: transferList: [workerPort],
L3566: // From node's documentation: https://nodejs.org/api/worker_threads.html
L3567: //
L3568: // Take care when launching worker threads from preload scripts (scripts loaded
L3569: // and run using the `-r` command line flag). Unless the `execArgv` option is
L3570: // explicitly set, new Worker threads automatically inherit the command line flags
Critical
Command Output Exfiltration
Source executes local commands and sends command output to an external endpoint.
dist/index.jsView on unpkg · L3553Findings
4 Critical5 High7 Medium5 Low
CriticalCredential Exfiltrationdist/index.js
CriticalCommand Output Exfiltrationdist/index.js
CriticalRemote Response Code Executiondist/index.js
CriticalTrigger Reachable Dangerous Capabilitydist/index.js
HighChild Processdist/index.js
HighEvaldist/index.js
HighCredential Redirect Persistencedist/index.js
HighTrigger Reachable Credential Exfiltrationdist/index.js
HighTrigger Reachable Command Output Exfiltrationdist/index.js
MediumSecret Patterndist/index.js
MediumDynamic Requiredist/index.js
MediumNetwork
Affected versions and remediation
This report applies to runlot@0.1.0-rc.162.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.162 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.