runlot@0.1.0-rc.163
⚠ Under reviewrunlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe source shows a user-triggered development runtime receiving project secrets, but the shipped executable could not be inspected beyond its unrecognized format. Because its handling of those secrets remains unresolved, manual review is warranted.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
When the CLI starts its configured development engine.
Impact
No secret disclosure is established; how the runtime handles those secrets could not be determined.
Mechanism
The CLI copies project secrets into the child process environment before launching the bundled runtime.
AI rationale
The source shows a user-triggered development runtime receiving project secrets, but the shipped executable could not be inspected beyond its unrecognized format. Because its handling of those secrets remains unresolved, manual review is warranted.
Evidence
package.jsondist/index.jsbin/linux-x64/runlot-dev-runtime.lpm-inspection-6Yjtxx/0-f52250d44b85.txt
Decision evidence
public snapshotAI called this Manual Review at 78.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest exposes the CLI and includes a bin directory, but declares no install lifecycle hook.
- The CLI can select and launch its bundled development runtime.
- Before launch, the CLI places project secrets in the runtime process environment.
- The available host analysis identifies the Linux runtime as an unrecognized executable and leaves its behavior unresolved.
Evidence against
- The unresolved executable is used as a development runtime; the inspected source does not establish secret disclosure or another attack.
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);
...
L113: async request(method, path, init) {
L114: const res = await fetch(new URL(path, this.opts.baseUrl), {
L115: ...init,
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L63815});
L3816: readFromStdout(stdout);
L3817: afterClose(null);
...
L3825: let worker = new worker_threads2.Worker(__filename, {
L3826: workerData: { workerPort, defaultWD, esbuildVersion: "0.24.2" },
L3827: transferList: [workerPort],
L3828: // From node's documentation: https://nodejs.org/api/worker_threads.html
L3829: //
L3830: // Take care when launching worker threads from preload scripts (scripts loaded
L3831: // and run using the `-r` command line flag). Unless the `execArgv` option is
L3832: // 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 · L3815Findings
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.163.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.163 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.