invoicerr-app/invoicerr - Open Source PR Review Scorecard

Invoicerr is a freelance-focused invoicing app that lets you create quotes, generate invoices, track payments, and collect secure signatures.

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

External PR Merge Rate: 10%

Response Time: -

First Timer Success: 50%

Frequently Asked Questions

Is invoicerr-app/invoicerr welcoming to first-time open-source contributors?

invoicerr-app/invoicerr has a recorded first-timer success rate of 50.0%. 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 invoicerr-app/invoicerr 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 51.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 51.4 places invoicerr-app/invoicerr in the B tier.

What is the external contributor pull request merge rate for invoicerr-app/invoicerr?

The external contributor pull request merge rate for invoicerr-app/invoicerr is 10.3%, based on public PR activity from non-core contributors.

Are there Good First Issues available in invoicerr-app/invoicerr?

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

invoicerr-app
invoicerr-app/invoicerrB•Solid731
GitHub
Back to Explorer
invoicerr-app

invoicerr-app/invoicerr

731
InactiveB•Solid(51/100)TypeScript

Invoicerr is a freelance-focused invoicing app that lets you create quotes, generate invoices, track payments, and collect secure signatures.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Maintainer

Warmth Score
7.8/10
Patience Score
8.2/10
Nitpick Rate
20%

Active maintainer team in invoicerr-app/invoicerr welcoming community pull requests and bug fixes.

Top PR Submission Do's

  • •Ensure code complies with repository style conventions
  • •Keep PRs focused and well-documented

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without context
  • •Do not break existing automated test suites
Response Velocity
-
No reviewer activity recorded

Average Response Latency

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

Merge Efficiency
10.3%
Selective PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
50.0%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
1 core
Single maintainer review bottleneck
Diagnostic Health HUD
10.3%
Merge Gauge
50.0%
1st-Timer
Community Vibe19/100

Embed C-Rank Badge

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

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

Active Good First Issues (2)

View on GitHub

Problem V23: dashboard metric tiles don't all share the same size. V27 (spotted while reviewing frames, not verbally flagged): the "Invoiced this month (EUR)" tile shows "0 EUR" together with a "-100%" trend badge at the same time, visually incoherent. Video (V23): https://youtu.be/-VGbYUSf0-c?t=128 (02:08) Frames (V27): f_0026.jpg, f_0036.jpg Current behavior The current dashboard (frontend/src/pages/(app)/dashboard.tsx) is a widget-contribution system (rebuilt after issues #417/#418/#419/#340) - different from what the existing documentation still describes (see Documentation below). V27 - the -100% figure is mathematically correct, not a math bug. Verified directly in frontend/src/components/widgets/widget-renderers/metric-widget.tsx, VariationChip: const diff = value - previousValue if (diff === 0) { /* "No change" */ } const isUp = diff > 0 const label = previousValue !== 0 ? t("widgets.metric.variationPercent", { percent: ((diff/previousValue)*100).toFixed(0) }) : t("widgets.

📅 Opened Oct 1, 2026💬 0 comments
Quality: 90/100Contribute

Problem A UX tester's review (https://youtu.be/-VGbYUSf0-c?t=162, 02:42, confirmed again on the invoice screen) found a right-hand sidebar block titled "About this VAT treatment" showing roughly 10 lines of raw explanatory text directly in the UI. Tester's words (translated): "Huge blocks of explanatory text... put that in a small info bubble. Don't display it like that." Current state (origin/dev) document-tax-warnings.tsx, rendered in the invoice detail page's totals sidebar: renders a title ("About this VAT treatment") and then maps each warning string into a plain paragraph, with no t() call and no collapse - the file's own comment admits this is deliberate, reusing the same always-visible style as other warning blocks. Important finding: this is NOT a fixed, finite catalog of cases like the correction-routes dialog fixed in #554/#564. The backend's own code comment on resolve-invoice-tax.ts states explicitly that these are English prose sentences composed with live, unbounded inte

📅 Opened Oct 1, 2026💬 0 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 invoicerr-app/invoicerr

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

Frequently Asked Questions - Contributing to invoicerr-app/invoicerr

01

Is invoicerr-app/invoicerr welcoming to first-time open-source contributors?

invoicerr-app/invoicerr has a recorded first-timer success rate of 50.0%. 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 51.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 51.4 places invoicerr-app/invoicerr in the Solid tier.

04

What is the external contributor pull request merge rate for invoicerr-app/invoicerr?

The external pull request merge rate is 10.3%. 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 invoicerr-app/invoicerr?

Yes, invoicerr-app/invoicerr currently has 2 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 invoicerr-app/invoicerr 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.