← Back to scan
File as GitHub Issue repo: gptme/gptme

Push this scan report to gptme/gptme

Click the green button below to open GitHub’s new-issue form, pre-filled with the report title, summary table, top findings, and an embedded score-card image. No authentication needed — you review on GitHub before submitting. Repobility is credited as the scanner.

Embedded score card image

This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.

Repobility score card

Issue title

SQL Injection Risk

Curate findings to include

Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.

Top 5 (default)
Severity Rule Title File:line
HIGH DKR006 Dockerfile pipes a remote script into a shell scripts/Dockerfile.eval:13
HIGH DKR006 Dockerfile pipes a remote script into a shell scripts/Dockerfile:48
HIGH SEC016 [SEC016] LLM Prompt Injection — User Input in AI Prompt: User-supplied text is interpolat… gptme/hooks/elicitation.py:202
HIGH SEC016 [SEC016] LLM Prompt Injection — User Input in AI Prompt: User-supplied text is interpolat… gptme/tools/morph.py:140
HIGH SEC004 [SEC004] SQL Injection Risk: String interpolation in SQL execution. Allows SQL injection. gptme/eval/dspy/tasks.py:513
HIGH SEC004 [SEC004] SQL Injection Risk: String interpolation in SQL execution. Allows SQL injection. gptme/eval/suites/practical15.py:175
HIGH SEC020 [SEC020] Secret Printed to Logs: Debug or diagnostic code appears to print a credential-b… gptme/hooks/token_awareness.py:69
HIGH SEC020 [SEC020] Secret Printed to Logs: Debug or diagnostic code appears to print a credential-b… gptme/context/adaptive_compressor.py:279
HIGH SEC020 [SEC020] Secret Printed to Logs: Debug or diagnostic code appears to print a credential-b… webui/src/utils/api.ts:486
HIGH JRN009 Secret-like setting is echoed into a password input value webui/src/components/settings/ServerApi…:187
HIGH JRN009 Secret-like setting is echoed into a password input value webui/src/components/SetupWizard.tsx:760
HIGH SEC005 [SEC005] Command Injection Risk: Unsafe shell execution or eval of user input. gptme/eval/main.py:53
HIGH SEC013 [SEC013] Path Traversal — User Input in File Path: User-controlled input used in file pat… webui/src/utils/taskApi.ts:214
HIGH SEC004 [SEC004] SQL Injection Risk: String interpolation in SQL execution. Allows SQL injection. gptme/hooks/form_autodetect.py:157
MED ERR002 [ERR002] Empty Catch Block: Empty catch blocks hide errors. webui/src/components/ConversationConten…:51
MED ERR001 [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides bugs. Even… gptme/tools/restart.py:146
MED ERR001 [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides bugs. Even… gptme/tools/_browser_playwright.py:228
MED ERR001 [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides bugs. Even… scripts/demo_capture.py:380
MED AUC001 [AUC001] No Repobility access matrix policy found: The repository uses web/API frameworks… —
MED DKR017 Dockerfile installs dependencies after copying the full source tree scripts/Dockerfile.computer:82
MED DKR009 Dockerfile separates apt update from install scripts/Dockerfile.computer:7
MED AIC003 Duplicated implementation block across source files gptme/util/install.py:10
MED AIC003 Duplicated implementation block across source files gptme/util/_telemetry.py:199
MED AIC003 Duplicated implementation block across source files gptme/tools/computer_transport.py:137
MED AIC003 Duplicated implementation block across source files gptme/tools/autocompact/scoring.py:139
MED AIC003 Duplicated implementation block across source files gptme/server/session_step.py:535
MED AIC003 Duplicated implementation block across source files gptme/eval/suites/behavioral/rate_limit…:56
MED AIC003 Duplicated implementation block across source files gptme/cli/cmd_agents.py:60
MED JRN002 Browser storage is used for session token material webui/src/stores/servers.ts:71
MED DKR001 Docker final stage has no non-root USER scripts/Dockerfile.dev:1
MED SEC017 [SEC017] Unbounded Input to LLM/External API: User input is passed to an LLM or external … gptme/hooks/elicitation.py:202
MED SEC017 [SEC017] Unbounded Input to LLM/External API: User input is passed to an LLM or external … gptme/tools/morph.py:140
MED WEB003 Public web service has no security.txt .well-known/security.txt
MED DKR014 Dockerfile copies broad context with incomplete .dockerignore scripts/Dockerfile.dev:24
MED DKR014 Dockerfile copies broad context with incomplete .dockerignore scripts/Dockerfile.computer:80
MED JRN003 Frontend API reference is not matched by discovered backend routes gptme/server/static/main.js:296
MED JRN003 Frontend API reference is not matched by discovered backend routes gptme/server/static/main.js:219
MED JRN003 Frontend API reference is not matched by discovered backend routes gptme/server/static/main.js:165
MED JRN003 Frontend API reference is not matched by discovered backend routes gptme/server/static/main.js:5
MED AUC002 [AUC002] Low visible authorization coverage in route inventory: Only 20.0% of discovered … —
MED AGT016 Codex session log reader may expose prompts or tool-call content gptme/hooks/workspace_agents.py:3
MED SEC005 [SEC005] Command Injection Risk: Unsafe shell execution or eval of user input. gptme/eval/swe_extra/swe_bench_test_spe…:137
MED SEC005 [SEC005] Command Injection Risk: Unsafe shell execution or eval of user input. gptme/prompts/context_cmd.py:54
LOW DKR008 .dockerignore misses sensitive defaults .dockerignore
LOW AIC002 Source file name looks like an AI patch artifact gptme/server/api_v2.py:1
LOW AIC002 Source file name looks like an AI patch artifact gptme/eval/suites/behavioral/noisy_work…:1
LOW AIC002 Source file name looks like an AI patch artifact gptme/eval/suites/behavioral/extract_fu…:1
Reset to top 5 47 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `gptme/gptme`

**Score: 45/100 (C)**  ·  58 findings  ·  scanned 2026-05-16 01:47 UTC  ·  248,359 LOC

| Severity | Count |
|---|---|
| CRITICAL | 0 |
| HIGH | 14 |
| MEDIUM | 29 |
| LOW | 4 |

📊 [Full filterable report](https://repobility.com/scan/852baae1-fabf-447b-9d40-b658b164911d/)  ·  ![scorecard](https://repobility.com/scan/852baae1-fabf-447b-9d40-b658b164911d/report.png?v=1778896061-s2)

### Top findings

1. **HIGH** `DKR006` — Dockerfile pipes a remote script into a shell
   `scripts/Dockerfile.eval:13`
2. **HIGH** `DKR006` — Dockerfile pipes a remote script into a shell
   `scripts/Dockerfile:48`
3. **HIGH** `SEC016` — LLM Prompt Injection — User Input in AI Prompt
   `gptme/hooks/elicitation.py:202`
4. **HIGH** `SEC016` — LLM Prompt Injection — User Input in AI Prompt
   `gptme/tools/morph.py:140`
5. **HIGH** `SEC004` — SQL Injection Risk
   `gptme/eval/dspy/tasks.py:513` · A03:2021 Injection

---

**Security note**: this issue is public. If any flagged finding is a real, exploitable vulnerability, please redirect to your `SECURITY.md` policy or open a [private security advisory](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability) instead. We're happy to close this and re-submit privately.

---

_Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/852baae1-fabf-447b-9d40-b658b164911d/_
Premium account
This scan was submitted by a Enterprise-tier account. Premium accounts have full outreach control â Repobility doesn't pre-fill the 'file as GitHub issue' button for paid users. You can still file the issue manually using the markdown body above (Copy markdown), or contact us if you'd like batch-filing enabled for your account.
Already filed
This repo publishes a SECURITY.md policy and the scan contains 10 Critical/High security finding(s). Public issue filing would violate coordinated disclosure. Submit privately via the project's security reporting channel.
Megaproject â high spam risk
Could not determine 'gptme/gptme' star count (GitHub API rate-limited or unreachable). When in doubt about repo size, prefer opening a focused PR or a discussion rather than an issue.
I read the warnings â override Cancel

The button opens GitHubâs new-issue page in a new tab. You will see the title + body pre-filled â review, edit if you want, then click GitHubâs "Submit new issue" button. Repobility never posts anything on your behalf.

For real security findings on big repos: use the project's SECURITY.md or private advisory flow instead of a public issue.