A Matrix community management platform
C-Rank Grade: B (Solid) - 46/100
External PR Merge Rate: 100%
Response Time: 3h
First Timer Success: -
the-draupnir-project/Draupnir has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in the-draupnir-project/Draupnir respond to incoming external pull requests in approximately 3.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 45.5 places the-draupnir-project/Draupnir in the B tier.
The external contributor pull request merge rate for the-draupnir-project/Draupnir is 100.0%, based on public PR activity from non-core contributors.
the-draupnir-project/Draupnir currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
A Matrix community management platform
Collaborative maintainer environment in the-draupnir-project/Draupnir. Reviews community pull requests with focus on project quality.
Discussions in the-draupnir-project/Draupnir focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/the-draupnir-project/Draupnir?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 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 16:00 to 20:00 UTC (16:00 - 20:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~14 hours (45% approval). Keep your diff compact for rapid review.
Since we're probably unlikely to make a decision to remove it entirely we should write this. And we should remove it from the default.yml config or whatever See #1104 among other issues We should also tell them about why an encrypted management room won't hide what commands are being used and also that for server acl, ban sync, and protections that dont' scan content, draupnir works fine in encrypted rooms without the encrypted device.
Like just not banning people in the mention limit protection or otherwise when their power level is above such a level or they are in the management room
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 the-draupnir-project/Draupnir, 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 the-draupnir-project/Draupnir acknowledge new external contributions in approximately 3 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
the-draupnir-project/Draupnir has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 hours. 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 45.5 places the-draupnir-project/Draupnir in the Solid tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, the-draupnir-project/Draupnir currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for the-draupnir-project/Draupnir 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.