io.github.DanceNitra/inspeximus

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_agent_grants.py: contains a hardcoded OpenAI API key (sk-a…AK (len 24)) — in an example/sample file; verify it is not a real key. tests/test_tenant_isolation_structural.py: contains a hardcoded OpenAI API key (sk-g…AK (len 25)) — in an example/sample file; verify it is not a real key. Reads secrets from the environment (e.g. inspeximus/_update.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 (inspeximus/claude_code.py: subprocess.* call; inspeximus/_update.py: outbound HTTP/socket call). has both shell/exec and destructive filesystem writes (inspeximus/claude_code.py: subprocess.* call; inspeximus/cli.py: destructive filesystem call (shutil.rmtree/os.remove/etc.)). discloses shell/exec capability: inspeximus/claude_code.py: subprocess.* call discloses shell/exec capability: inspeximus/timestamp.py: subprocess.* call discloses broad/destructive filesystem access: 4 files (inspeximus/cli.py, inspeximus/timestamp.py, inspeximus/timestamp.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 2.24.1 (minor 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, code.claude.com, cursor.com, dancenitra.github.io, docs.cline.bot, docs.devin.ai, ec.europa.eu, evil.test, example.com, example.invalid, example.test, github.com, learn.chatgpt.com, notion.so, pypi.org, uri.etsi.org, www.notion.so, www.w3.org, x.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 tracking behavior — disclosure