freescout-help-desk/freescout - Open Source PR Review Scorecard

FreeScout — Free self-hosted omnichannel AI-powered helpdesk & shared mailbox

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

External PR Merge Rate: 19%

Response Time: -

First Timer Success: 13%

Frequently Asked Questions

Is freescout-help-desk/freescout welcoming to first-time open-source contributors?

freescout-help-desk/freescout has a recorded first-timer success rate of 12.5%. 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 freescout-help-desk/freescout 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.8 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.8 places freescout-help-desk/freescout in the A tier.

What is the external contributor pull request merge rate for freescout-help-desk/freescout?

The external contributor pull request merge rate for freescout-help-desk/freescout is 19.3%, based on public PR activity from non-core contributors.

Are there Good First Issues available in freescout-help-desk/freescout?

freescout-help-desk/freescout currently has 7 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

freescout-help-desk
freescout-help-desk/freescoutA•Welcoming4.6k
GitHub
Back to Explorer
freescout-help-desk

freescout-help-desk/freescout

4,594
Active (30d)A•Welcoming(64/100)PHP

FreeScout — Free self-hosted omnichannel AI-powered helpdesk & shared mailbox

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Strict Quality Architect

Warmth Score
7.1/10
Patience Score
7.5/10
Nitpick Rate
37%

Balanced & professional review environment in freescout-help-desk/freescout. 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
19.3%
Selective PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
12.5%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
14 core
Highly collaborative maintainer core
Diagnostic Health HUD
19.3%
Merge Gauge
12.5%
1st-Timer
Community Vibe11/100

Embed C-Rank Badge

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

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

Active Good First Issues (5)

View on GitHub

When we get tickets that we want to merge, they often come in batches, e.g. 20 e-mails with very similar or the exact same subject and from the same sender. The current way of merging tickets is the Merge dialog in a ticket itself, which is based on a search and a small list of similar tickets. That ticket list, however, is very minimal. It only contains the ticket number and the subject. So it is often necessary to verify that the ticket we are selecting is actually the one we think it is by opening it. That's tiresome. Using the ticket list would make it much easier to identify which tickets should be merged, as it shows much more information about the tickets themselves. Like this (mockup): Information displayed in the ticket merge dialog: ticket number subject Information displayed in the ticket list: ticket number subject customer name customer e-mail content preview reception time Some other ticketing systems also have that feature, and I very much like it for such cases.

📅 Opened Sep 24, 2026💬 1 comment
Quality: 90/100Contribute

We want to better track our customers history to understand previous problems or patterns. We can't see anything that they might be cc'ed on or to'ed additionally too

📅 Opened Sep 21, 2026💬 0 comments
Quality: 35/100Contribute

PHP version: (unknown, please advise if needed) FreeScout version: 1.8.239 Database: (unknown) Are you using CloudFlare: No (mailbox fetch is direct; CloudFlare only fronts the site that sends the email) Are you using non-official modules: No Summary A single mailbox emailing itself creates two separate conversations from what is confirmed to be the same email (identical Message-Id header). Only one fetch method is configured for the mailbox (verified), so this isn't a duplicate-fetch-method misconfiguration. Setup One FreeScout mailbox: [email protected] An external service sends mail via JMAP (Fastmail/MessagingEngine relay) with From: [email protected] and To: [email protected] (self-addressed - the sending identity and the destination mailbox are the same address). Only one incoming-fetch method is active for this mailbox (confirmed in Settings > Mailboxes > Incoming). Actual behavior Two separate conversations are created, both with subject [Uninstall Fee

📅 Opened Sep 15, 2026💬 4 comments
Quality: 90/100Contribute

Problem On the conversations list, the Customer column is too narrow. Long customer names get cut off, the email gets truncated, and the thread counter badge next to the name is pushed out of view. For a customer with 100+ threads the badge is not visible at all. At the same time, the Assigned To column takes far more space than it needs. A single short name gets roughly the same width as the whole Conversation column, so the subject and preview get squeezed and clipped. Adjusting the widths in the browser (wider Customer column, narrower Assigned To, Conversation gets the remaining space) fixes it: the full customer name, the counter badge and the email all fit, and the subject gets much more room. Suggestion Give the Customer column more width so name, counter and email fit. Give the Assigned To column a fixed, smaller width. Let the Conversation column take the remaining space. Recommendation (longer term) The conversation list is a legacy HTML table with hard-coded column widths

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

PHP version: not to hand (this is a feature request, not a bug report — happy to provide if useful) FreeScout version: 1.8.230 (from the pinned nfrastack/freescout:2.2.0 image; may have moved since) Database: MariaDB Are you using CloudFlare: No Are you using non-official modules: No Feature request: an option to paste as plain text in the conversation editor When agents paste content into a reply (from Word, Outlook, Google Docs, or another mail client), the source HTML comes in as-is and cannot be fully cleaned afterwards. Background colours, table/div layout and fonts survive, so the reply that reaches the customer carries formatting from wherever the text came from. Looking at convEditorInit() in public/js/main.js, the plain-text paste handler already exists, but it is only applied to chat conversations: // Allow to insert only plain text in chats if (convIsChat()) { options.callbacks.onPaste = function (e) { var bufferText = ((e.originalEvent || e).clipboardData || w

📅 Opened Aug 27, 2026💬 2 comments
Quality: 90/100Contribute
Looking for more PHP beginner tasks?Explore PHP 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 freescout-help-desk/freescout

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

Frequently Asked Questions - Contributing to freescout-help-desk/freescout

01

Is freescout-help-desk/freescout welcoming to first-time open-source contributors?

freescout-help-desk/freescout has a recorded first-timer success rate of 12.5%. 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.8 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.8 places freescout-help-desk/freescout in the Welcoming tier.

04

What is the external contributor pull request merge rate for freescout-help-desk/freescout?

The external pull request merge rate is 19.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 freescout-help-desk/freescout?

Yes, freescout-help-desk/freescout currently has 7 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 freescout-help-desk/freescout 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.