← Back to scan
File as GitHub Issue repo: wenxig/dongtai-sub

Push this scan report to wenxig/dongtai-sub

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

undici: GHSA-vrm6-8vpv-qv8q

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 SEC029 [SEC029] Server-Side Request Forgery (SSRF) — outbound HTTP from user input: Outbound HTT… src/output/mihomo.ts:62
HIGH SEC128 [SEC128] Async function without await — fire-and-forget Promise (AI mistake): Async call … src/output/index.ts:10
HIGH MINED115 Action `oven-sh/setup-bun` pinned to mutable ref `@v2` .github/workflows/hourly-write.yml:31
HIGH MINED115 Action `actions/checkout` pinned to mutable ref `@v6` .github/workflows/hourly-write.yml:25
HIGH GHSA-vrm6-8vpv-qv8q undici: GHSA-vrm6-8vpv-qv8q bun.lock
HIGH GHSA-v9p9-hfj2-hcw8 undici: GHSA-v9p9-hfj2-hcw8 bun.lock
HIGH GHSA-f269-vfmq-vjvj undici: GHSA-f269-vfmq-vjvj bun.lock
HIGH CORE_NO_TESTS No test files found —
MED DEPCUR-NPM npm package `jsdom` is 1 major version(s) behind (^28.0.0 -> 29.1.1) package.json
MED GHSA-phc3-fgpg-7m6h undici: GHSA-phc3-fgpg-7m6h bun.lock
MED GHSA-4992-7rv2-5pvq undici: GHSA-4992-7rv2-5pvq bun.lock
MED GHSA-2mjp-6q6p-2qxm undici: GHSA-2mjp-6q6p-2qxm bun.lock
LOW DEPCUR-GHA GitHub Action `oven-sh/setup-bun@v2` is minor version(s) behind (latest v2.2.0) .github/workflows/hourly-write.yml:31
LOW DEPCUR-NPM npm package `oxlint` is minor version(s) behind (^1.51.0 -> 1.68.0) package.json
LOW DEPCUR-NPM npm package `oxfmt` is minor version(s) behind (^0.36.0 -> 0.53.0) package.json
LOW CORE_NO_LICENSE No LICENSE file —
INFO MINED054 [MINED054] Ts As Any: Casting to any (as any) bypasses type checking entirely. src/output/mihomo.ts:205
INFO MINED043 [MINED043] Http Not Https: Hardcoded http:// (not localhost) for endpoints that handle cr… src/output/mihomo.ts:222
INFO DEPCUR-GHA GitHub Action `actions/checkout@v6` is patch version(s) behind (latest v6.0.3) .github/workflows/hourly-write.yml:25
INFO DEPCUR-NPM npm package `@types/jsdom` is patch version(s) behind (^28.0.0 -> 28.0.3) package.json
INFO DEPCUR-NPM npm package `@types/bun` is patch version(s) behind (^1.3.9 -> 1.3.14) package.json
Reset to top 5 21 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `wenxig/dongtai-sub`

**Score: 82/100 (C+)**  ·  21 findings  ·  scanned 2026-06-05 18:20 UTC  ·  311 LOC

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

📊 [Full filterable report](https://repobility.com/scan/04712ea2-73a9-4e52-9647-18548a6c60d8/)  ·  ![scorecard](https://repobility.com/scan/04712ea2-73a9-4e52-9647-18548a6c60d8/report.png?v=1780683655-s2)

### Top findings

1. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input
   `src/output/mihomo.ts:62` · A10:2021 SSRF
2. **HIGH** `SEC128` — Async function without await — fire-and-forget Promise (AI mistake)
   `src/output/index.ts:10`
3. **HIGH** `MINED115` — Action `oven-sh/setup-bun` pinned to mutable ref `@v2`
   `.github/workflows/hourly-write.yml:31` · ✓ Repobility
4. **HIGH** `MINED115` — Action `actions/checkout` pinned to mutable ref `@v6`
   `.github/workflows/hourly-write.yml:25` · ✓ Repobility
5. **HIGH** `GHSA-vrm6-8vpv-qv8q` — undici: GHSA-vrm6-8vpv-qv8q
   `bun.lock`

---

**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/04712ea2-73a9-4e52-9647-18548a6c60d8/_
Megaproject â high spam risk
Could not determine 'wenxig/dongtai-sub' 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.