← Back to scan
File as GitHub Issue repo: Misaka-blog/chromego_merge

Push this scan report to Misaka-blog/chromego_merge

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

Bare except continues silently: Bare `except:` (or `except Exception

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 SEC078 [SEC078] Python: requests without timeout: requests.get/post without a timeout will hang … sing-box.py:9
HIGH SEC029 [SEC029] Server-Side Request Forgery (SSRF) — outbound HTTP from user input: Outbound HTT… meta_merge.py:18
HIGH MINED115 [MINED115] Action `actions/setup-python` pinned to mutable ref `@v2`: `uses: actions/setu… .github/workflows/merge.yml:19
HIGH MINED115 [MINED115] Action `actions/checkout` pinned to mutable ref `@v2`: `uses: actions/checkout… .github/workflows/merge.yml:16
MED MINED111 [MINED111] Bare except continues silently: Bare `except:` (or `except Exception:`) that r… merge.py:387
MED MINED124 [MINED124] requirements.txt: `geoip2` has no version pin: Unpinned pip requirement means … requirements.txt:2
LOW SEC124 [SEC124] TOCTOU file access (os.access then open): Check-then-use file pattern (access/ex… sing-box.py:15
LOW AIC003 Duplicated implementation block across source files meta_merge.py:4
INFO MINED067 [MINED067] Python Requests No Timeout: requests.get/post/etc. without timeout= can hang f… sing-box.py:9
Reset to top 5 9 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `Misaka-blog/chromego_merge`

**Score: 75/100 (B)**  ·  9 findings  ·  scanned 2026-06-05 15:07 UTC  ·  734 LOC

| Severity | Count |
|---|---|
| CRITICAL | 0 |
| HIGH | 4 |
| MEDIUM | 2 |
| LOW | 2 |

📊 [Full filterable report](https://repobility.com/scan/8af2125d-6eee-404c-90f0-1c9ed2519c73/)  ·  ![scorecard](https://repobility.com/scan/8af2125d-6eee-404c-90f0-1c9ed2519c73/report.png?v=1780672079-s2)

### Top findings

1. **HIGH** `SEC078` — Python: requests without timeout
   `sing-box.py:9` · A05:2021 Security Misconfiguration
2. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input
   `meta_merge.py:18` · A10:2021 SSRF
3. **HIGH** `MINED115` — Action `actions/setup-python` pinned to mutable ref `@v2`: `uses
   `.github/workflows/merge.yml:19` · ✓ Repobility
4. **HIGH** `MINED115` — Action `actions/checkout` pinned to mutable ref `@v2`: `uses
   `.github/workflows/merge.yml:16` · ✓ Repobility
5. **MEDIUM** `MINED111` — Bare except continues silently: Bare `except:` (or `except Exception
   `merge.py:387` · ✓ Repobility

---

**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/8af2125d-6eee-404c-90f0-1c9ed2519c73/_
Megaproject â high spam risk
Could not determine 'Misaka-blog/chromego_merge' 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.
Open in GitHub to file this issue 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.