@melaya/runner@1.1.31
Run Melaya AI pipelines locally with your own LM Studio or Ollama models
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo install-time attack or directly malicious payload is present in this snapshot, but the package is an active remote-code loader that executes server-supplied Python with sensitive runtime context. This is a substantial unresolved supply-chain capability and should be warned rather than published as clean.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs melaya-runner and starts an assistant or pipeline session.
Impact
A server or token-authorized endpoint can supply Python code that runs with the runner process's environment and connector credentials.
Mechanism
Remote Python bundle download, cache write, and PYTHONPATH-based execution.
AI rationale
No install-time attack or directly malicious payload is present in this snapshot, but the package is an active remote-code loader that executes server-supplied Python with sensitive runtime context. This is a substantial unresolved supply-chain capability and should be warned rather than published as clean.
Evidence
dist/sharedVendor.jsdist/connection.jsdist/pythonEnv.js~/.melaya-runner/shared/~/.melaya-runner/agentscope/~/.melaya-runner/venv/dist/assistantHost.py
Network endpoints1
api.melaya.org
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- On a normal runner connection, it downloads Python source selected by the server.
- The downloaded files are written under the user's Melaya cache without a publisher-held signature.
- Assistant startup adds that cache to Python's import path and launches Python with inherited environment variables and supplied credentials.
- It also bootstraps a virtual environment and installs a broad Python dependency set at runtime.
Evidence against
- package.json has no install, preinstall, or postinstall hook.
- The browser provisioner only downloads Chromium when its explicit authorization option is enabled.
- The observed network and process behavior is activated by running the CLI, not by package installation.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
8 flaggeddist/codeWorker.jsView file
51// model (--experimental-permission / --permission): fs read/write
L52: // limited to the scratch dir, child_process and worker_threads denied.
L53: //
High
Child Process
Package source references child process execution.
dist/codeWorker.jsView on unpkg · L51288// ulimit -t: hard CPU time in seconds.
L289: // We use /bin/sh -c "ulimit ...; exec sandbox-exec ..." so both limits
L290: // apply before the Node process starts. This is a soft-then-hard pair;
High
dist/browserProvisioner.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @melaya/runner@1.0.93
matchedIdentity = npm:QG1lbGF5YS9ydW5uZXI:1.0.93
similarity = 0.538
summary = stored previous version shares package body but lacks this dangerous source file
Findings
1 Critical6 High4 Medium6 Low
CriticalPrevious Version Dangerous Deltadist/browserProvisioner.js
HighChild Processdist/codeWorker.js
HighShelldist/codeWorker.js
HighSandbox Evasion Gated Capabilitydist/browserProvisioner.js
HighCloud Metadata Accessdist/browserAuthz.js
HighRuntime Package Installdist/lumaLogin.js
HighSemantic Analysis Limiteddist/linkedinLogin.js#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperdist/localRagIngest.py
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
Affected versions and remediation
This report applies to @melaya/runner@1.1.31.
See all versions of @melaya/runner for other recorded verdicts.
- Review the evidence and your use of @melaya/runner@1.1.31 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.