runlot@0.1.0-rc.168
⚠ Under reviewrunlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe source confirms that a CLI command can start a bundled executable, but the executable is an unrecognized artifact whose behavior could not be determined. No attack is established; manual review is needed to resolve this material uncertainty.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs a CLI command that starts the development runtime.
Impact
The executable's effects cannot be determined from the inspected source and artifact analysis, so no specific attack is confirmed.
Mechanism
The CLI searches for and can invoke the packaged runtime executable; the available artifact analysis could not characterize its behavior.
AI rationale
The source confirms that a CLI command can start a bundled executable, but the executable is an unrecognized artifact whose behavior could not be determined. No attack is established; manual review is needed to resolve this material uncertainty.
Evidence
dist/index.js.lpm-inspection-nQaEwC/0-4d86c713d1c9.txtbin/linux-x64/runlot-dev-runtime
Decision evidence
public snapshotAI called this Manual Review at 72.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest exposes `dist/index.js` as the CLI entrypoint, and that CLI locates the bundled `runlot-dev-runtime` executable.
- The shipped runtime is a 12 MB unrecognized artifact; its offline inspection could not determine its behavior.
- The prepared dependency manifest identifies PGlite as a PostgreSQL and WASM database library; its package includes JavaScript and CommonJS entrypoints.
Evidence against
- The inspected source confirms the bundled runtime is invoked, but does not establish what it does.
- The prepared PGlite files show module and WASM initialization; this does not resolve the separate runtime executable.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
11 flaggeddist/index.jsView file
6const __filename = __runlotFilePath(import.meta.url);
L7: const __dirname = __runlotDirname(__filename);
L8: var __create = Object.create;
...
L47: // ../../packages/api/src/index.ts
L48: function base64urlJson(v) {
L49: const bytes = new TextEncoder().encode(JSON.stringify(v));
...
L54: function gitQuery(ref, path) {
L55: const q = new URLSearchParams();
L56: if (ref !== "") q.set("ref", ref);
...
L126: async request(method, path, init) {
L127: const res = await fetch(new URL(path, this.opts.baseUrl), {
L128: ...init,
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L64288});
L4289: readFromStdout(stdout);
L4290: afterClose(null);
...
L4298: let worker = new worker_threads2.Worker(__filename, {
L4299: workerData: { workerPort, defaultWD, esbuildVersion: "0.24.2" },
L4300: transferList: [workerPort],
L4301: // From node's documentation: https://nodejs.org/api/worker_threads.html
L4302: //
L4303: // Take care when launching worker threads from preload scripts (scripts loaded
L4304: // and run using the `-r` command line flag). Unless the `execArgv` option is
L4305: // 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 · L4288Findings
4 Critical5 High5 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
MediumDynamic Requiredist/index.js
MediumNetwork
MediumEnvironment Vars
Medium
Affected versions and remediation
This report applies to runlot@0.1.0-rc.168.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.168 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.