indmdev/Free-Telegram-Store-Bot
indmdev/Free-Telegram-Store-BotClick 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.
urllib3: GHSA-38jv-5279-wg99
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `indmdev/Free-Telegram-Store-Bot` **Score: 74/100 (C-)** · 48 findings · scanned 2026-06-05 14:00 UTC · 2,870 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 8 | | MEDIUM | 32 | | LOW | 7 | 📊 [Full filterable report](https://repobility.com/scan/65df4b6b-94ac-4ace-960a-880d5b0966b9/) ·  ### Top findings 1. **HIGH** `MINED009` — Floats For Money `utils.py:54` · CWE-682 · ✓ Repobility 2. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input `utils.py:90` · A10:2021 SSRF 3. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input `config.py:86` · A10:2021 SSRF 4. **HIGH** `GHSA-gm62-xv2j-4w53` — urllib3: GHSA-gm62-xv2j-4w53 `requirements.txt` 5. **HIGH** `GHSA-38jv-5279-wg99` — urllib3: GHSA-38jv-5279-wg99 `requirements.txt` --- **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/65df4b6b-94ac-4ace-960a-880d5b0966b9/_
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.