@melaya/runner@1.1.14
Run Melaya AI pipelines locally with your own LM Studio or Ollama models
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe runtime code exposes a consequential authenticated Luma registration capability through the saved browser session, while the inspected source does not resolve user authorization for every request. The Claude credential transfer is for model discovery at Anthropic, and no install-time attack or confirmed unauthorized account action was found.
Decision evidence
public snapshot- The runner reads saved Claude credentials for model discovery and sends a valid access token to Anthropic’s models endpoint.
- The Luma bridge reuses saved browser state for Luma requests and uses a real browser fingerprint to help registration requests pass Cloudflare checks.
- The CLI starts model detection, while Luma login and result handling are activated through runner socket events.
- The bridge restricts forwarded requests to allowed hosts and GET or POST methods; the inspected source does not establish an unwanted account action.
- The manifest has no install lifecycle hook; its prepublishOnly script runs the build.
- Codex credential detection checks for a saved login but reads model names from a cache rather than sending the token.
- The inspected Luma flow is a product connector using the saved session; the source does not establish that its registration action is performed without a user-requested pipeline.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/codeWorker.jsView on unpkg · L51Package source invokes a package manager install command at runtime.
Findings
Affected versions and remediation
This report applies to @melaya/runner@1.1.14.
See all versions of @melaya/runner for other recorded verdicts.
- Review the evidence and your use of @melaya/runner@1.1.14 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.