io.github.troybrandonc-bit/omem

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.

  repository linkage verified

• Credential hygiene

  pass15% of grade

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

  Reads secrets from the environment (e.g. omem/mcp_bootstrap.py) — the recommended intake shape. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.

• 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 (omem/_server/backups.py: subprocess.* call; omem/__init__.py: outbound HTTP/socket call). has both shell/exec and destructive filesystem writes (omem/_server/backups.py: subprocess.* call; omem/mcp_bootstrap.py: destructive filesystem call (shutil.rmtree/os.remove/etc.)). discloses shell/exec capability: omem/_server/backups.py: subprocess.* call discloses broad/destructive filesystem access: 4 files (omem/mcp_bootstrap.py, omem/_server/backups.py, omem/_server/backups.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 0.3.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, a, accounts.google.com, api.github.com, api.groq.com, api.openai.com, api.stripe.com, api.web3forms.com, commons.omem-cloud.com, console., docs.omem.dev, f, fonts.googleapis.com, fonts.gstatic.com, github.com, gmail.googleapis.com, infrastructure.omem-cloud.com, mail.google.com, mock.my.salesforce.com, n, nextjs.org, oauth2.googleapis.com, react.dev, reactjs.org, slack.com, stripe.com, use.typekit.net, www.googleapis.com, www.w3.org, x.

• Transport config

  warn10% of grade

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

  manifest/source references tracking behavior — disclosure