io.github.navapbc/rebar

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

  fail25% of grade

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

  Python build script executes at build time: subprocess in build script

• 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/rebar/config.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

  fail15% of grade

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

  HIGH: executes content derived from a network response (src/rebar/_engine/ticket_graph/_links.py: passes a network response into an exec/eval call). has both shell/exec and destructive filesystem writes (src/rebar/__init__.py: subprocess.* call; src/rebar/_engine/acli-integration.py: destructive filesystem call (shutil.rmtree/os.remove/etc.)). discloses shell/exec capability: 24 files (src/rebar/__init__.py, src/rebar/_engine.py, src/rebar/cli.py, +21 more) discloses broad/destructive filesystem access: 21 files (src/rebar/_engine/acli-integration.py, src/rebar/_engine/ticket-archive-markers-backfill.sh, src/rebar/_engine/ticket-compact.sh, +18 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.12.0 (minor bump): new capability primitive(s) in source: fs-write, http-client, subprocess; new hardcoded outbound host/BCC destination(s): example, example.atlassian.net, example.com, github.com, id.atlassian.com, jira.example.com, navasage.atlassian.net, support.atlassian.com, test.atlassian.net, x, your-org.atlassian.net.

• Transport config

  fail10% of grade

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

  source performs runtime self-update / download-and-execute (bypasses version_behavior); manifest/source references Tracking behavior — disclosure