io.github.MervinPraison/praisonai

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. praisonai/__init__.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: shell/exec capability AND network egress together — download-and-execute risk (praisonai/cli/main.py: subprocess.* call; praisonai/cli/features/n8n.py: outbound HTTP/socket call). HIGH: shell/exec capability AND destructive filesystem writes together (praisonai/cli/main.py: subprocess.* call; praisonai/auto.py: open(…, 'w'/'a'/'x') write-mode file access). discloses shell/exec capability: praisonai/cli/main.py: subprocess.* call discloses shell/exec capability: praisonai/code/tools/execute_command.py: subprocess.* call with shell=True (command-injection prone) discloses shell/exec capability: praisonai/deploy.py: subprocess.* call discloses shell/exec capability: praisonai/setup/build.py: subprocess.* call discloses shell/exec capability: praisonai/setup/post_install.py: subprocess.* call discloses shell/exec capability: praisonai/setup/setup_conda_env.py: subprocess.* call discloses shell/exec capability: praisonai/setup.py: subprocess.* call discloses shell/exec capability: praisonai/train.py: subprocess.* call discloses shell/exec capability: praisonai/train_vision.py: subprocess.* call discloses shell/exec capability: praisonai/ui/code.py: subprocess.* call discloses shell/exec capability: praisonai/upload_vision.py: subprocess.* call discloses shell/exec capability: tests/test.py: subprocess.* call with shell=True (command-injection prone) discloses shell/exec capability: tests/test_runner.py: subprocess.* call discloses dynamic code execution: tests/test_custom_tools_fix.py: uses eval/exec/__import__ discloses broad/destructive filesystem access: praisonai/auto.py: open(…, 'w'/'a'/'x') write-mode file access discloses broad/destructive filesystem access: praisonai/chainlit_ui.py: open(…, 'w'/'a'/'x') write-mode file access discloses broad/destructive filesystem access: praisonai/cli/features/n8n.py: open(…, 'w'/'a'/'x') write-mode file access discloses broad/destructive filesystem access: praisonai/cli/features/todo.py: open(…, 'w'/'a'/'x') write-mode file access discloses broad/destructive filesystem access: praisonai/cli/features/workflow.py: open(…, 'w'/'a'/'x') write-mode file access discloses broad/destructive filesystem access: praisonai/cli/main.py: open(…, 'w'/'a'/'x') write-mode file access discloses broad/destructive filesystem access: praisonai/cli/main.py: destructive filesystem call (shutil.rmtree/os.remove/etc.) discloses broad/destructive filesystem access: praisonai/deploy.py: open(…, 'w'/'a'/'x') write-mode file access discloses broad/destructive filesystem access: praisonai/train.py: open(…, 'w'/'a'/'x') write-mode file access discloses broad/destructive filesystem access: praisonai/train.py: destructive filesystem call (shutil.rmtree/os.remove/etc.) discloses broad/destructive filesystem access: praisonai/train_vision.py: open(…, 'w'/'a'/'x') write-mode file access discloses broad/destructive filesystem access: praisonai/train_vision.py: destructive filesystem call (shutil.rmtree/os.remove/etc.) discloses broad/destructive filesystem access: praisonai/ui/agents.py: open(…, 'w'/'a'/'x') write-mode file access discloses broad/destructive filesystem access: praisonai/ui/components/aicoder.py: open(…, 'w'/'a'/'x') write-mode file access discloses broad/destructive filesystem access: praisonai/ui/db.py: destructive filesystem call (shutil.rmtree/os.remove/etc.) discloses broad/destructive filesystem access: praisonai/upload_vision.py: open(…, 'w'/'a'/'x') write-mode file access discloses broad/destructive filesystem access: praisonai/upload_vision.py: destructive filesystem call (shutil.rmtree/os.remove/etc.) discloses broad/destructive filesystem access: tests/test_custom_tools_fix.py: open(…, 'w'/'a'/'x') write-mode file access discloses broad/destructive filesystem access: tests/test_n8n_integration.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.MervinPraison/[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