Palm1r/QodeAssist
Palm1r/QodeAssistClick 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.
This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.
Path Traversal — User Input in File Path
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `Palm1r/QodeAssist` **Score: 83/100 (C)** · 43 findings · scanned 2026-05-31 01:22 UTC · 95,805 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 5 | | MEDIUM | 3 | | LOW | 30 | 📊 [Full filterable report](https://repobility.com/scan/aeaea856-35f0-42df-ab0d-ac0223210dfd/) ·  ### Top findings 1. **HIGH** `SEC085` — JS: child_process.exec with non-literal `UpdateStatusWidget.cpp:68` 2. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input `ChatView/FileItem.cpp:39` · A10:2021 SSRF 3. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input `ChatView/ChatHistoryStore.cpp:186` · A10:2021 SSRF 4. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input `ChatView/ChatCompressor.cpp:79` · A10:2021 SSRF 5. **HIGH** `SEC013` — Path Traversal — User Input in File Path `LLMClientInterface.hpp:63` · A01:2021 Broken Access Control (path traversal) --- **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/aeaea856-35f0-42df-ab0d-ac0223210dfd/_
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.