io.github.FantasyLab-ai/aurora

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

  warn15% of grade

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

  tests/test_contract_action_types.py: contains a hardcoded Slack incoming webhook (http…ET (len 49)) — in an example/sample file; verify it is not a real key. tests/test_llm_providers.py: contains a hardcoded OpenAI API key (sk-s…ak (len 30)) — in an example/sample file; verify it is not a real key. Reads secrets from the environment (e.g. aurora_mcp/http_server.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 (aurora_sdk/runner.py: subprocess.* call; fantasyai/aurora/agents/data_acquisition.py: outbound HTTP/socket call). has both shell/exec and destructive filesystem writes (aurora_sdk/runner.py: subprocess.* call; fantasyai/aurora/audit.py: open(…, 'w'/'a'/'x') write-mode file access). discloses shell/exec capability: 4 files (aurora_sdk/runner.py, fantasyai/aurora/export.py, fantasyai/aurora/provenance/ledger.py, +1 more) discloses broad/destructive filesystem access: fantasyai/aurora/audit.py: open(…, 'w'/'a'/'x') write-mode file access discloses broad/destructive filesystem access: fantasyai/aurora/knowledge_bank/packs/downloader.py: open(…, 'w'/'a'/'x') write-mode file access discloses broad/destructive filesystem access: fantasyai/aurora/knowledge_bank/packs/installer.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

  unscannable10% of grade

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

  no prior version to diff (first sight of io.github.FantasyLab-ai/[email protected]); version-drift / rug-pull cannot be evaluated. Cold-start risk is covered by point-in-time checks (injection_surface, supply_chain, credential_hygiene), not here.

• Transport config

  warn10% of grade

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

  sends telemetry to third-party SDK (amplitude) — disclosure, verify opt-in; manifest/source references telemetry behavior — disclosure