io.github.JeanFrancoisGagne/crapkit

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

  warn25% of grade

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

  no resolvable repository linked to the package (provenance unverifiable)

• 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. src/crapkit/analyze.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 destructive filesystem writes (src/crapkit/cli/admin.py: subprocess.* call with shell=True (command-injection prone); src/crapkit/churn_log.py: open(…, 'w'/'a'/'x') write-mode file access). discloses shell/exec capability: 9 files (src/crapkit/cli/admin.py, src/crapkit/cli/claude_hook.py, src/crapkit/cli/reports.py, +6 more) discloses broad/destructive filesystem access: src/crapkit/churn_log.py: open(…, 'w'/'a'/'x') write-mode file access discloses broad/destructive filesystem access: src/crapkit/gitio.py: destructive filesystem call (shutil.rmtree/os.remove/etc.) discloses broad/destructive filesystem access: src/crapkit/mutate_pool.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 0.4.15 (minor bump): new capability primitive(s) in source: child_process, fs-write, subprocess; new hardcoded outbound host/BCC destination(s): github.com, jeanfrancoisgagne.github.io, raw.githubusercontent.com.

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