io.github.3M1RY33T/loci

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.

  tests/test_core.py: embeds a PRIVATE KEY block. (in an example/sample file — lower severity, but a real key here still leaks.) Reads secrets from the environment (e.g. evals/fit.py) — the recommended intake shape.

• Permission scope

  warn15% of grade

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

  references credential paths: src/loci/redact.py: references a credential path (id_rsa) has both shell/exec and destructive filesystem writes (evals/corpus.py: subprocess.* call; evals/corpus.py: destructive filesystem call (shutil.rmtree/os.remove/etc.)). discloses shell/exec capability: 7 files (evals/corpus.py, evals/real_corpus.py, evals/scale.py, +4 more) discloses broad/destructive filesystem access: 6 files (evals/corpus.py, evals/fit.py, evals/real_corpus.py, +3 more) Capability DISCLOSURE, not a verdict: static analysis sees the primitive is present and reachable, not whether its use is attacker-controlled.

• Version behavior

  unscannable10% of grade

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

  no prior version to diff (first sight of io.github.3M1RY33T/[email protected]); version-drift / rug-pull cannot be evaluated. Cold-start risk is covered by point-in-time checks (injection_surface, supply_chain, credential_hygiene), not here.

• 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 telemetry behavior — disclosure