io.github.mapsmith-ai/mapsmith

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

  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/mapsmith/discovery_log.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 (site/build.py: subprocess.* call; site/build.py: destructive filesystem call (shutil.rmtree/os.remove/etc.)). discloses shell/exec capability: site/build.py: subprocess.* call discloses shell/exec capability: src/mapsmith/stacks.py: subprocess.* call discloses dynamic code execution: src/mapsmith/engines/raster.py: uses eval()/exec() discloses broad/destructive filesystem access: site/build.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.3.0 (minor bump): new capability primitive(s) in source: dynamic-eval, fs-write, net, subprocess; new hardcoded outbound host/BCC destination(s): 127.0.0.1, b.s3.amazonaws.com, data.example, evil, evil.tld, example.com, example.invalid, github.com, host, raw.githubusercontent.com, tile.openstreetmap.org, u.

• 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