@melaya/runner@1.1.68
Run Melaya AI pipelines locally with your own LM Studio or Ollama models
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe flagged execution and network behavior resolves to runner provisioning, provider-specific model discovery, and requested browser sign-in. The reviewed lifecycle and runtime paths establish no concrete attack behavior.
Decision evidence
public snapshot- The manifest lists only a build-only prepublishOnly lifecycle script. The inspected dependencies are CLI formatting and parsing libraries, and the main entry only exports functions.
- Credential-based model discovery reads local provider credentials and uses provider APIs; it returns model names rather than forwarding those credentials to Melaya.
- The CLI starts model discovery, the connection refreshes it, and the runner sends the model list over its authenticated Melaya socket.
- Failure reporting sends a stage and bounded runtime details with the runner token to the configured server or the Melaya API fallback.
- Browser sign-in is session-requested, stores browser state locally, and the Luma bridge binds to loopback and restricts hosts.
- Python and browser setup follow runner provisioning or sign-in flows; Chromium downloads require an explicit authorization flag or occur during Luma sign-in.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/uvBootstrap.jsView on unpkg · L20Findings
Affected versions and remediation
This report applies to @melaya/runner@1.1.68.
See all versions of @melaya/runner for other recorded verdicts.
- Review the evidence and your use of @melaya/runner@1.1.68 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.