actualbudget/actual - Open Source PR Review Scorecard

A local-first personal finance app

C-Rank Grade: A (Welcoming) - 63/100

External PR Merge Rate: 61%

Response Time: -

First Timer Success: 36%

Frequently Asked Questions

Is actualbudget/actual welcoming to first-time open-source contributors?

actualbudget/actual has a recorded first-timer success rate of 35.6%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in actualbudget/actual respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 63.2 C-Rank™ score (A Tier) represent?

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 63.2 places actualbudget/actual in the A tier.

What is the external contributor pull request merge rate for actualbudget/actual?

The external contributor pull request merge rate for actualbudget/actual is 60.6%, based on public PR activity from non-core contributors.

Are there Good First Issues available in actualbudget/actual?

actualbudget/actual currently has 11 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

actualbudget
actualbudget/actualA•Welcoming29.4k
GitHub
Back to Explorer
actualbudget

actualbudget/actual

29,418
InactiveA•Welcoming(63/100)TypeScript

A local-first personal finance app

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Constructive Code Reviewer

Warmth Score
8.2/10
Patience Score
8.4/10
Nitpick Rate
22%

Balanced & professional review environment in actualbudget/actual. Maintains strict focus on technical quality and test standards.

Top PR Submission Do's

  • •Add unit tests with >80% coverage for modified code paths
  • •Run repository linter and code formatters locally before pushing
  • •Link relevant GitHub issue ID in PR description pre-flight checklist

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without referencing an existing issue
  • •Do not mix refactoring and feature logic into a single commit
  • •Do not ping maintainers repeatedly within 24 hours of opening
Response Velocity
-
No reviewer activity recorded

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
60.6%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
35.6%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
108 core
Highly collaborative maintainer core
Diagnostic Health HUD
60.6%
Merge Gauge
35.6%
1st-Timer
Community Vibe35/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for actualbudget/actual
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/actualbudget/actual)](https://getmerged.abhishekco.de/actualbudget/actual?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

What happened? If you click Edit Dashboard on the dashboard page before all the graphs has finished loading, they grey out as expected but the ones off screen at the bottom do not finish loading - if you click finish editing, they don't go back to loading until you refresh. How can we reproduce the issue? Go to reports when you have a lot of widgets on your dashboard Click Edit Dashboard while they are still loading Scroll Down The ones that have not started loading don't finish loading Click Finish Editing they do not restart Expected behaviour - they keep loading but remain greyed out, when you Finish Editing they are like you had never clicked Edit Where are you hosting Actual? Docker What browsers are you seeing the problem on? Firefox Operating System Linux

📅 Opened Sep 30, 2026💬 0 comments
Quality: 50/100Contribute

What happened? When looking at an account in the mobile UI, if "Hide reconciled transactions" is on, then the running balance of the earliest shown transaction is wrong. The error is not present in the desktop UI. How can we reproduce the issue? Demo budget with a few unreconciled transactions: 2026-09-29-Test Budget.zip Running balance without and with the reconciled transactions shown. The "-10.00" running balance should be "1785.98" in this case. Data looks correct in desktop UI, even when hiding reconciled transactions: Where are you hosting Actual? Docker What browsers are you seeing the problem on? Chrome Operating System Windows 11

📅 Opened Sep 29, 2026💬 1 comment
Quality: 50/100Contribute

What happened? Category data is lost upon QIF file import shich is is a blocker for any new Actual user wanting to migrate all historical data from other budgeting app. Statement file content has L field values present and matching already exsiting categories defined in Actual budget. All other data transation fields are successfuly parsed and present for imported transations. !Type:Bank D18/08/2026 PA Place MPurchase Nr. 01232234 T-9,4 LUsual Expenses:Food ^ D31/08/2026 PYOLO MSarary T50, CX LIncome:Income ^ Preliminary exploration hints that root cause is that categories from file upon import are parsed as string whereas later expected to be mapped to category UUID and that intermediate mapping is missing hence behaves as if category is not found resulting in blank field for transaction. Sample statement file attached -actualStatement.qif.zip How can we reproduce the issue? Create new clean budget in Actual desktop app (used categories are created along with new budget) Create new

📅 Opened Sep 26, 2026💬 2 comments
Quality: 50/100Contribute

What happened? When selecting a custom theme and then adding custom CSS, I would expect that reverting to a "stock" theme would ignore the custom CSS that was added when using a custom theme (or maybe was the feature designed to also be able to customize stock themes?). Nonetheless, there is a visual glitch when selecting the "System Default" option from the theme selector after applying custom CSS. The "Custom CSS is active" button/url remains visible when reverting to a stock theme. Furthermore, the custom CSS gets applied over the stock theme. How can we reproduce the issue? I was able to reproduce the issue in the demo version of Actual following the steps below : Select a custom theme and add custom CSS Revert to any of the stock themes selection See the "Custom CSS is active" button still being present. When reverting to the "System Default" theme selection, the "Custom CSS is active" button is stacked below the "Light" theme dropdown selection. Where are you hosting Actual? D

📅 Opened Sep 7, 2026💬 9 comments
Quality: 50/100Contribute

What happened? A scheduled transaction with Automatically add transaction enabled does not post automatically on its due date. How can we reproduce the issue? Steps / behaviour: Schedule is configured to automatically post. On the scheduled date, the schedule shows as Due. The transaction appears in the account register as a greyed-out/upcoming transaction. It does not automatically post. Closing and reopening Actual does not cause it to post. Selecting Post transaction today manually works immediately. Expected: The transaction should automatically become a posted transaction on the scheduled date. Actual: It remains an upcoming/grey transaction until manually posted. Where are you hosting Actual? Desktop App (Electron) What browsers are you seeing the problem on? Firefox Operating System Windows 11

📅 Opened Sep 3, 2026💬 3 comments
Quality: 90/100Contribute
Looking for more TypeScript beginner tasks?Explore TypeScript GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for actualbudget/actual

When evaluating whether to contribute to actualbudget/actual, 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 actualbudget/actual acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 60.6% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to actualbudget/actual

01

Is actualbudget/actual welcoming to first-time open-source contributors?

actualbudget/actual has a recorded first-timer success rate of 35.6%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 63.2 C-Rank™ score represent?

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 63.2 places actualbudget/actual in the Welcoming tier.

04

What is the external contributor pull request merge rate for actualbudget/actual?

The external pull request merge rate is 60.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in actualbudget/actual?

Yes, actualbudget/actual currently has 11 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for actualbudget/actual 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.