flow-mn/flow - Open Source PR Review Scorecard

A personal finance tracker app built with love, and Flutter

C-Rank Grade: B (Solid) - 54/100

External PR Merge Rate: 90%

Response Time: -

First Timer Success: 67%

Frequently Asked Questions

Is flow-mn/flow welcoming to first-time open-source contributors?

flow-mn/flow has a recorded first-timer success rate of 66.7%. Repositories ranked B 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 flow-mn/flow 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 54.4 C-Rank™ score (B 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 54.4 places flow-mn/flow in the B tier.

What is the external contributor pull request merge rate for flow-mn/flow?

The external contributor pull request merge rate for flow-mn/flow is 90.5%, based on public PR activity from non-core contributors.

Are there Good First Issues available in flow-mn/flow?

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

flow-mn
flow-mn/flowB•Solid499
GitHub
Back to Explorer
flow-mn

flow-mn/flow

499
InactiveB•Solid(54/100)Dart

A personal finance tracker app built with love, and Flutter

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

Warmth Score
8.0/10
Patience Score
8.4/10
Nitpick Rate
25%

Highly welcoming maintainers in flow-mn/flow. Prompt code reviews with positive guidance for new contributors.

Top PR Submission Do's

  • •Ensure code complies with the project coding style
  • •Keep PRs scoped to a single concern
  • •Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit PRs without linking an issue
  • •Do not break existing tests without fixing them
  • •Do not mix unrelated refactors in a single PR
Response Velocity
-
No reviewer activity recorded

Average Response Latency

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

Merge Efficiency
90.5%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
66.7%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
1 core
Single maintainer review bottleneck
Diagnostic Health HUD
90.5%
Merge Gauge
66.7%
1st-Timer
Community Vibe56/100

Embed C-Rank Badge

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

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

Active Good First Issues (1)

View on GitHub

Description When an sms is recieved which is in a particular format trigger a workflow that will extract the details from the sms like amt spent, account,etc and then add a transaction with prefilled values and then send a notification to the user to review the transaction added Additional Context No response

📅 Opened Feb 23, 2026💬 5 comments
Quality: 70/100Contribute
Looking for more Dart beginner tasks?Explore Dart 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 flow-mn/flow

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

Frequently Asked Questions - Contributing to flow-mn/flow

01

Is flow-mn/flow welcoming to first-time open-source contributors?

flow-mn/flow has a recorded first-timer success rate of 66.7%. Repositories ranked Solid 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 54.4 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 54.4 places flow-mn/flow in the Solid tier.

04

What is the external contributor pull request merge rate for flow-mn/flow?

The external pull request merge rate is 90.5%. 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 flow-mn/flow?

Yes, flow-mn/flow currently has 1 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 flow-mn/flow 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.