io.github.GCTRL-TECH/gctrl

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

  warn25% of grade

  Tool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).

  tool "gctrl_store" description: bare 'IMPORTANT:' prose in a description (tag form is high-confidence; prose is warn). tool "borghive_store" description: bare 'IMPORTANT:' prose in a description (tag form is high-confidence; prose is warn).

• Supply chain

  pass25% of grade

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

  repository linkage verified

• Credential hygiene

  pass15% of grade

  How the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.

  No hardcoded secrets, secret-shaped tool parameters, or leaked keys found. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.

• Permission scope

  pass15% of grade

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

  No shell-exec, unbounded/sensitive filesystem, or download-and-run primitives found in scanned source. PASS = no static red flag. Static scanning is blind to code fetched or executed at runtime.

• Version behavior

  warn10% of grade

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

  vs prior 1.1.0 (minor bump): new tool "gctrl_extract" appeared; new tool "borghive_extract" appeared; new tool "gctrl_query" appeared; new tool "borghive_query" appeared; new tool "gctrl_search_entities" appeared; new tool "borghive_search_entities" appeared; new tool "gctrl_get_dossier" touches a sensitive surface (email/exec/net/fs); new tool "borghive_get_dossier" touches a sensitive surface (email/exec/net/fs); new tool "gctrl_list_graphs" appeared; new tool "borghive_list_graphs" appeared; new tool "gctrl_fuse" appeared; new tool "borghive_fuse" appeared; new tool "gctrl_distill" appeared; new tool "borghive_distill" appeared; new tool "gctrl_wiki_page" touches a sensitive surface (email/exec/net/fs); new tool "borghive_wiki_page" touches a sensitive surface (email/exec/net/fs); new tool "gctrl_search_chunks" appeared; new tool "borghive_search_chunks" appeared; new tool "gctrl_get_entity" touches a sensitive surface (email/exec/net/fs); new tool "borghive_get_entity" touches a sensitive surface (email/exec/net/fs); new tool "gctrl_get_neighbors" appeared; new tool "borghive_get_neighbors" appeared; new tool "gctrl_shortest_path" appeared; new tool "borghive_shortest_path" appeared; new tool "gctrl_list_conflicts" appeared; new tool "borghive_list_conflicts" appeared; new tool "gctrl_detect_communities" touches a sensitive surface (email/exec/net/fs); new tool "borghive_detect_communities" touches a sensitive surface (email/exec/net/fs); new tool "gctrl_wiki_graph" appeared; new tool "borghive_wiki_graph" appeared; new tool "gctrl_ingest_repo" touches a sensitive surface (email/exec/net/fs); new tool "borghive_ingest_repo" touches a sensitive surface (email/exec/net/fs); new tool "gctrl_pin_dossier" appeared; new tool "borghive_pin_dossier" appeared; new tool "gctrl_memory_feedback" appeared; new tool "borghive_memory_feedback" appeared; new tool "gctrl_memory_health" touches a sensitive surface (email/exec/net/fs); new tool "borghive_memory_health" touches a sensitive surface (email/exec/net/fs); new tool "gctrl_run_maintenance" touches a sensitive surface (email/exec/net/fs); new tool "borghive_run_maintenance" touches a sensitive surface (email/exec/net/fs); new tool "gctrl_get_user_profile" touches a sensitive surface (email/exec/net/fs); new tool "borghive_get_user_profile" touches a sensitive surface (email/exec/net/fs); new tool "gctrl_list_ontologies" appeared; new tool "borghive_list_ontologies" appeared; new tool "gctrl_list_extractions" appeared; new tool "borghive_list_extractions" appeared; new tool "gctrl_store" touches a sensitive surface (email/exec/net/fs); new tool "borghive_store" touches a sensitive surface (email/exec/net/fs); new tool "gctrl_schema" appeared; new tool "borghive_schema" appeared; new tool "gctrl_find_file" touches a sensitive surface (email/exec/net/fs); new tool "gctrl_get_sync_status" appeared; new tool "gctrl_ingest_file" touches a sensitive surface (email/exec/net/fs); new tool "gctrl_set_privacy_mode" touches a sensitive surface (email/exec/net/fs); new tool "borghive_set_privacy_mode" touches a sensitive surface (email/exec/net/fs); new tool "gctrl_code_index" touches a sensitive surface (email/exec/net/fs); new tool "gctrl_code_symbol" touches a sensitive surface (email/exec/net/fs); new tool "gctrl_code_trace" appeared; new tool "gctrl_code_impact" touches a sensitive surface (email/exec/net/fs); new tool "gctrl_code_architecture" appeared.

• Transport config

  unscannable10% of grade

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

  local stdio server: no remote transport or auth surface, and no phone-home/telemetry signal found in source. Absence of transport findings is NOT a safety guarantee — phone-home hosts can be constructed at runtime and defeat static analysis.