@melaya/runner@1.0.76

One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source

Explicit execution of melaya-runner with --token, then authenticated server events

Melaya-controlled jobs can run locally with inherited environment, package-provided credentials, local model access, and selected local files for RAG workflows; no hidden install-time persistence or agent control-surface hijack was found.

Authenticated cloud-controlled local Python runner

After explicit CLI startup, the runner connects to Melaya and waits for authenticated server events. Those events can cause it to download cached Python support code, build a venv, write server-provided Python/config into temp directories, and spawn it locally. This is a substantial remote execution capability, but it is the declared runner function and was not delivered through npm lifecycle execution or foreign AI-agent control-surface mutation.

Static inspection found dangerous but package-aligned runner behavior that requires explicit CLI use and a Melaya token, with no install-time execution, persistence, destructive action, raw credential exfiltration, or AI-agent hijack. Because the package intentionally enables cloud-dispatched local code execution with weak local signature verification, warn rather than block.