@melaya/runner@1.1.77
Run Melaya AI pipelines locally with your own LM Studio or Ollama models
AI Security Review
scanned 6h ago · by lpm-firewall-aiThe flagged credential accesses are used for model discovery against the credential-owning services, and discovery is part of the runner’s stated purpose. The source also shows that Luma login is user-triggered and that metadata addresses are classified in browser authorization code; no malicious behavior was established.
Decision evidence
public snapshot- The package exposes a runner CLI and a library entry point; its only lifecycle script is prepublishOnly, which runs the build.
- Provider discovery sends Claude and GitHub credentials to their respective providers to retrieve model information.
- The CLI starts provider discovery as part of runner startup and publishes the resulting model list.
- Luma sign-in opens a visible browser only after the Melaya server requests login.
- The browser authorization code classifies cloud metadata addresses for protection.
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.77.
See all versions of @melaya/runner for other recorded verdicts.
- Review the evidence and your use of @melaya/runner@1.1.77 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.