io.github.skynetcmd/m3-memory

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

  fail25% of grade

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

  Python build script executes at build time: subprocess in build script, network call in build script

• Credential hygiene

  warn15% of grade

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

  tests/test_chatlog_redaction.py: contains a hardcoded OpenAI API key (sk-a…ab (len 27)) — in an example/sample file; verify it is not a real key. tests/test_chatlog_redaction.py: contains a hardcoded JWT (eyJh…5c (len 155)) — in an example/sample file; verify it is not a real key. Reads secrets from the environment (e.g. setup.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 (m3_memory/installer.py: subprocess.* call; m3_memory/installer.py: outbound HTTP/socket call). has both shell/exec and destructive filesystem writes (m3_memory/installer.py: subprocess.* call; m3_memory/installer.py: open(…, 'w'/'a'/'x') write-mode file access). discloses shell/exec capability: m3_memory/installer.py: subprocess.* call discloses dynamic code execution: m3_memory/cli.py: uses eval()/exec() discloses broad/destructive filesystem access: m3_memory/installer.py: open(…, 'w'/'a'/'x') write-mode file access discloses broad/destructive filesystem access: m3_memory/installer.py: destructive filesystem call (shutil.rmtree/os.remove/etc.) 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 2026.8.29.1 (patch bump): new capability primitive(s) in source: child_process, dynamic-eval, fs-write, http-client, subprocess; new hardcoded outbound host/BCC destination(s): 127.0.0.1, github.com, x.

• Transport config

  unscannable10% of grade

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

  local stdio server: no remote transport or auth surface, and no phone-home/telemetry signal found in source. Absence of transport findings is NOT a safety guarantee — phone-home hosts can be constructed at runtime and defeat static analysis.