@melaya/runner@1.1.75
Run Melaya AI pipelines locally with your own LM Studio or Ollama models
AI Security Review
scanned 6h ago · by lpm-firewall-aiThe lifecycle script only builds for publishing, and the startup credential reads inspected are used for requests to the corresponding AI provider APIs to discover models. The metadata alert is a protective deny rule, while the Luma browser install is tied to a sign-in flow.
Decision evidence
public snapshot- The only lifecycle script is prepublishOnly, which runs the build; there is no install hook.
- The CLI scans providers when the runner starts to discover available local models.
- Claude credentials are sent to api.anthropic.com for model discovery, and GitHub credentials to api.github.com for Copilot token exchange.
- Browser authorization explicitly denies cloud metadata endpoints.
- The Luma browser setup runs as part of the Luma login flow, rather than at install or import time.
- Provider discovery reads local provider credentials, but the observed requests send them to their corresponding provider APIs for model availability.
- The scanner’s metadata alert points to a deny rule, not code that collects metadata credentials.
Source & flagged code
20 flaggedPackage source references child process execution.
dist/uvBootstrap.jsView on unpkg · L20Source file is highly similar to a previously finalized malicious package; route for source-aware review.
dist/uvBootstrap.jsView on unpkgFindings
Affected versions and remediation
This report applies to @melaya/runner@1.1.75.
See all versions of @melaya/runner for other recorded verdicts.
- Review the evidence and your use of @melaya/runner@1.1.75 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.