不用記帳｜ALL SET：自架個人財務中樞，整合銀行、信用卡、投資與電子發票。
C-Rank Grade: B (Solid) - 48/100
External PR Merge Rate: 17%
Response Time: 1d
First Timer Success: -
TedLin1993/all-set-tw has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in TedLin1993/all-set-tw respond to incoming external pull requests in approximately 26.4 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 48.5 places TedLin1993/all-set-tw in the B tier.
The external contributor pull request merge rate for TedLin1993/all-set-tw is 16.7%, based on public PR activity from non-core contributors.
TedLin1993/all-set-tw currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
不用記帳｜ALL SET：自架個人財務中樞，整合銀行、信用卡、投資與電子發票。
Strict review standards in TedLin1993/all-set-tw. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in TedLin1993/all-set-tw focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/TedLin1993/all-set-tw?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 01:00 to 05:00 UTC (01:00 - 05:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~17 hours (21% approval). Large PRs (>500 lines) take ~127 hours (15% approval). Keep your diff compact for rapid review.
你好，我綁定永豐銀行後，發現信用卡與銀行帳戶的資料同步似乎都有一些問題，整理如下： 1. 信用卡未出帳消費被誤判為收入 綁定永豐銀行後，有成功抓到信用卡交易資料，但發現： 信用卡已出帳的消費：顯示正常，會被正確計算為支出。 信用卡尚未出帳的消費：會被判定為「收入」，而不是「支出」。 因此在查看收支紀錄與統計時，未出帳的信用卡消費會造成收入與支出的數據不正確。 想請問這是否是交易類型判斷或資料同步上的問題？不確定目前是否有可能改善，讓信用卡未出帳消費也能正確判定為支出。 2. 永豐銀行帳戶無法抓取 另外，綁定永豐銀行後，信用卡資料可以正常抓取，但銀行帳戶卻無法抓取，並顯示： 此機構沒有銀行帳戶。 不確定這是否與我使用的是永豐大戶數位帳戶有關。不過我可以在「永豐行動銀行 App」中正常
環境 自架 Cloudflare Workers + Browser Rendering，版本 96afdb0。 玉山銀行連接器，首次手動驗證／同步。 重現經過與觀察 在資料來源啟動玉山銀行同步，依畫面點擊同步按鈕。 使用者隨後收到玉山銀行寄出之「登入成功」通知。 站台仍顯示「需要處理」，沒有成功同步紀錄，且提示「上次同步：Waiting failed: 20000ms exceeded」。經檢查後 ，Cloudflare Page Observability 回報進度曾到達「[esun debug] login succeeded, collecting account data」，隨後立刻回報以下錯誤： { "level": "error", "event": "esun_browser_login_failed", "errorType": "TimeoutError", "$workers": { "truncated": false, "scriptName": "taiwan-fin-hub", "scriptVersion": { "id": "f8efe769-18a3-4a39-b30d-ec7feaf67aa9" }, "eventType": "fetch", "executionModel": "stateless", "event": { "request": { "method": "POST", "url": "/api/connectors/esun/sync", "path": "/api/connectors/esun/sync" } } }, "$metadata": { "id
環境 自架 Cloudflare Workers + Browser Rendering，程式版本 0dde103（包含 #170 的新版 MyBank 登入首頁修正）。 國泰世華連接器 cathaybk，首次手動驗證／同步。 重現經過與觀察 在資料來源啟動國泰世華同步，依畫面選擇驗證管道並輸入收到的一次性驗證碼。 使用者隨後收到銀行寄出的「登入成功」通知。 站台仍顯示「需要處理」，沒有成功同步紀錄。檢查 D1 時，sync_jobs 的 last_status 是 needs_user_action，last_error 為「國泰世華驗證碼錯誤或已逾時，請重新輸入或取得驗證碼。」；稍後連接器詳情又顯示驗證工作階段已逾時。 銀行的登入通知不等於爬取及資料寫入已完成；目前只能確認銀行端有發送成功通知，但專案未進入成功狀態。尚未取得足以判定 OTP、信任裝置設定或後續頁面擷取哪一段失敗的證據。 預期／實際 預期：若銀行端已接受 OTP，連接器繼續
需求 希望能新增 台北富邦銀行（012） 與 兆豐銀行（017） 的連接器，同步存款帳戶餘額／交易明細與信用卡帳單。 現況 目前 connectorCatalog 沒有這兩家。 集保 e 存摺的 SETTLEMENT_BANK_NAMES 已包含 012 台北富邦銀行 與 017 兆豐銀行，但那只涵蓋證券交割帳戶，拿不到一般存款帳戶與信用卡。 翻過既有 issue 與 PR，沒有找到這兩家的規劃或進行中的工作。 想請教 這兩家是否已在規劃中？ 若沒有，是否歡迎外部 PR？（參考 #169 凱基銀行由外部貢獻者完成的模式） 對連接模式有沒有建議？依 docs/004-connector-development.md 的分類，這兩家看起來比較接近 browser_captcha_session，但想先確認是否有偏好用 App API 的方向。 感謝維護這個專案。
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to TedLin1993/all-set-tw, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of TedLin1993/all-set-tw acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 16.7% were successfully merged into the primary branch.
TedLin1993/all-set-tw has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 48.5 places TedLin1993/all-set-tw in the Solid tier.
The external pull request merge rate is 16.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, TedLin1993/all-set-tw currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for TedLin1993/all-set-tw are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.