io.github.eidetic-works/nucleus

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

  pass25% of grade

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

  Scanned 180 text field(s); no instruction-injection patterns found. PASS = no static red flag. A server can serve different tool descriptions at runtime (the rug-pull class), which static scanning cannot see.

• 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.

  Reads secrets from the environment (e.g. examples/basic_usage.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 (index.js: imports child_process and calls exec/spawn; src/mcp_server_nucleus/__init__.py: open(…, 'w'/'a'/'x') write-mode file access). discloses shell/exec capability: index.js: imports child_process and calls exec/spawn discloses shell/exec capability: .smithery/shttp/module.js: imports child_process discloses shell/exec capability: src/mcp_server_nucleus/hypervisor/locker.py: subprocess.* call discloses broad/destructive filesystem access: 8 files (src/mcp_server_nucleus/__init__.py, src/mcp_server_nucleus/runtime/common.py, scripts/demo_governance.py, +5 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 1.15.0 (patch bump): new tool "nucleus_governance" touches a sensitive surface (email/exec/net/fs); new tool "nucleus_features" touches a sensitive surface (email/exec/net/fs); new tool "nucleus_sessions" touches a sensitive surface (email/exec/net/fs); new tool "nucleus_tasks" appeared; new tool "nucleus_sync" touches a sensitive surface (email/exec/net/fs); new tool "nucleus_next_message" appeared; new tool "nucleus_relay_subscribe" touches a sensitive surface (email/exec/net/fs); new tool "nucleus_ccr_arm" appeared; new tool "nucleus_wakeup_wait" appeared; new tool "nucleus_orchestration" touches a sensitive surface (email/exec/net/fs); new tool "nucleus_telemetry" appeared; new tool "nucleus_slots" touches a sensitive surface (email/exec/net/fs); new tool "nucleus_infra" touches a sensitive surface (email/exec/net/fs); new tool "nucleus_agents" touches a sensitive surface (email/exec/net/fs); new tool "nucleus_federation" appeared; new tool "nucleus_engrams" touches a sensitive surface (email/exec/net/fs); new tool "nucleus_relay" touches a sensitive surface (email/exec/net/fs); new tool "nucleus_route" appeared; new tool "nucleus_audit" appeared; new tool "nucleus_delegate" touches a sensitive surface (email/exec/net/fs); new tool "nucleus_lane_init" appeared; new tool "nucleus_lane_start" appeared; new tool "nucleus_lane_stop" appeared; new tool "nucleus_lane_status" appeared; new tool "nucleus_lane_feedback" appeared; new tool "nucleus_plan_execute" touches a sensitive surface (email/exec/net/fs); new tool "nucleus_plan_import" touches a sensitive surface (email/exec/net/fs); new tool "nucleus_plan_list" appeared; new capability primitive(s) in source: child_process, fs-write, subprocess; new hardcoded outbound host/BCC destination(s): github.com, json-schema.org, lodash.com, npms.io, openjsf.org, underscorejs.org.

• 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