io.github.darknodebros/elesync

What we checked

Six static checks, weighted by risk. Every result reflects only what could be observed in the published package and repository — never intent.

• Injection surface

  unscannable25% of grade

  Tool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).

  No tool descriptions, server instructions, prompts, or resources were fetched; nothing to scan for injection.

• Supply chain

  pass25% of grade

  Package provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.

  Python build script has no build-time network/exec; repository linkage verified

• Credential hygiene

  warn15% of grade

  How the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.

  elesync/static/dashboard-connect.js: assigns a literal to token (${_g…)} (len 20)) — non-provider secret literal; prefer environment intake. tests/test_packaging.py: assigns a literal to token ($VER…EN (len 13)) — non-provider secret literal; prefer environment intake. Reads secrets from the environment (e.g. elesync/__init__.py) — the recommended intake shape.

• Permission scope

  warn15% of grade

  Declared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.

  has both shell/exec and network egress — capable of download-and-run, though no such path was observed (elesync/embeddings.py: subprocess.* call; elesync/gemini.py: outbound HTTP/socket call). has both shell/exec and destructive filesystem writes (elesync/embeddings.py: subprocess.* call; elesync/archive.py: open(…, 'w'/'a'/'x') write-mode file access). discloses shell/exec capability: 4 files (elesync/embeddings.py, elesync/remote.py, elesync/tunnel.py, +1 more) discloses broad/destructive filesystem access: 4 files (elesync/archive.py, elesync/backups.py, elesync/cli.py, +1 more) Capability DISCLOSURE, not a verdict: static analysis sees the primitive is present and reachable, not whether its use is attacker-controlled.

• Version behavior

  fail10% of grade

  Diff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).

  vs prior 1.24.13 (patch bump): new capability primitive(s) in source: child_process, fs-write, http-client, net, subprocess; new hardcoded outbound host/BCC destination(s): 127.0.0.1, aistudio.google.com, api.anthropic.com, api.github.com, api.openai.com, cfg, client.example, demo.ngrok-free.dev, elephant.localhost.run, elesync.dev, example.com, example.ngrok-free.dev, example.test, generativelanguage.googleapis.com, github.com, grok.example.test, myhost, ollama.com, purple.lhr.life, rclone.org, your-domain.example.

• Transport config

  fail10% of grade

  Remote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.

  source performs runtime self-update / download-and-execute (bypasses version_behavior); manifest/source references tracking behavior — disclosure