Stoat for Web – browser app for Stoat
C-Rank Grade: S (Elite) - 68/100
External PR Merge Rate: 76%
Response Time: -
First Timer Success: 73%
stoatchat/for-web has a recorded first-timer success rate of 73.3%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in stoatchat/for-web 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.
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 68.4 places stoatchat/for-web in the S tier.
The external contributor pull request merge rate for stoatchat/for-web is 76.2%, based on public PR activity from non-core contributors.
stoatchat/for-web currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in stoatchat/for-web. Prompt code reviews with positive guidance for new contributors.
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/stoatchat/for-web?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 04:00 UTC (04:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (95% approval). Large PRs (>500 lines) take ~115 hours (34% approval). Keep your diff compact for rapid review.
What happened? if you just send $$ it will just send an invisible line. Not a big bug but I can see people abusing it edit: I am on archlinux using firefox but it also happend in the electron app 2026-09-11.16-42-52.mp4
What happened? When a user is given a role, it unlocks new channels, fairly simple. When removing the role from the person, those channels are hidden, so far so good. However, when giving back that role or when giving a role that has the same or more permissions, it won't update the client, requiring a refresh. Video demonstration provided 1080p.60FPS.mp4
What happened? It's happening on settings too + some words aren't translated. I can help if needed with translations since im a native speaker (for free) if needed but generally AI can do it too.
What happened? Some places where date and time will display wrong: On a sent message, hovering over the time will display the date as dd/MM/yyyy regardless of locale and settings. In the dynamic date-time using <t:, this is forced to be the format EEEE, dd MMM yyyy hh:mm (truncated with different formatters) regardless of locale, but with translated weekday and month. It is displayed as 12-hour time, with leading zero, so 06:00 and 18:00 will both display as "06:00". Hovering over the dynamic date-time (<t:), this will always display the popup using English in the fixed format EEE, dd MMM yyyy HH:mm:ss 'GMT' in the GMT-timezone. Checking someone's profile, the date for joining Stoat and a server is always displayed as dd MMM yyyy regardless of locale, with translated month. In both hovering on a dynamic date-time, as well as the date for joining Stoat/server, would be better written in the short format, since the user has control over this. Some place format numbers wrong
What happened? When you post a link in Dark Mode, the embedded URL seems to stay in light mode. It makes the linked text white on light gray, which is a bit hard to read. Here's an example of what it looks like:
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 stoatchat/for-web, 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 stoatchat/for-web acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 76.2% were successfully merged into the primary branch.
stoatchat/for-web has a recorded first-timer success rate of 73.3%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 68.4 places stoatchat/for-web in the Elite tier.
The external pull request merge rate is 76.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, stoatchat/for-web currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for stoatchat/for-web 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.