@melaya/runner@1.1.66
Run Melaya AI pipelines locally with your own LM Studio or Ollama models
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe lifecycle entry is a prepublish build, and the runtime findings resolve to provider model discovery and runner setup behavior. Credential transfers inspected use provider endpoints or the selected runner server; no concrete attack behavior was found.
Decision evidence
public snapshot- package.json defines prepublishOnly as a build command; it has no install lifecycle hook.
- CLI model detection and periodic refresh read saved provider login state. The Claude token goes to Anthropic’s model endpoint, and the GitHub token exchange goes to GitHub’s Copilot endpoint.
- Fatal-startup reporting is limited to failure-stage metadata, uses the supplied server or the Melaya default, and can be disabled with MELAYA_RUNNER_NO_TELEMETRY.
- The connection code sets assistant-host approval flags from per-turn connector data.
- Inspected dependency snapshots identify chalk and ora as terminal libraries and commander as a command-line parser.
- The reviewed setup and browser paths implement runner workflows; browser downloads require explicit authorization, URL checks restrict browser actions, and Luma forwarding limits hosts to Luma domains.
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.66.
See all versions of @melaya/runner for other recorded verdicts.
- Review the evidence and your use of @melaya/runner@1.1.66 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.