Turns the documentation you already write into tests that run. A failing test means your product and your docs disagree, and names the section.
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 75%
Response Time: 1d
First Timer Success: 33%
truecourse-ai/truecourse has a recorded first-timer success rate of 33.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in truecourse-ai/truecourse respond to incoming external pull requests in approximately 33.6 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 66.7 places truecourse-ai/truecourse in the A tier.
The external contributor pull request merge rate for truecourse-ai/truecourse is 75.3%, based on public PR activity from non-core contributors.
truecourse-ai/truecourse currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Turns the documentation you already write into tests that run. A failing test means your product and your docs disagree, and names the section.
Strict review standards in truecourse-ai/truecourse. Ensure PR scope matches issue requirements closely before requesting review.
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/truecourse-ai/truecourse?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 23:00 UTC (23:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 21:00 to 01:00 UTC (21:00 - 01:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~22 hours (94% approval). Large PRs (>500 lines) take ~161 hours (34% approval). Keep your diff compact for rapid review.
Allow users to create custom analysis rules and enable/disable existing rules from the UI and CLI. What needs to be done Enable/Disable Rules Backend: Rules are already stored in the rules table with an enabled boolean field Add PATCH /api/repos/:id/rules/:ruleKey endpoint to toggle enabled status The pipeline already reads rules via getEnabledRules() which filters by enabled: true Frontend (Rules tab): Add a toggle switch on each rule in the Rules panel to enable/disable it Changes take effect on the next analysis run Show visual distinction for disabled rules (grayed out) CLI: truecourse rules — list all rules with enabled/disabled status truecourse rules enable <ruleKey> — enable a rule truecourse rules disable <ruleKey> — disable a rule Custom Rules Backend: Add POST /api/rules endpoint to create custom rules Custom rules should support: key — unique identifier (e.g., custom/no-console-in-services) category — code, service, module, database name and description ty
Allow users to dismiss violations they've reviewed and decided are not actionable — false positives, accepted technical debt, or intentional patterns. What needs to be done Backend New status: dismissed Add dismissed as a valid violation status alongside new, unchanged, resolved Applies to both architecture violations (violations table) and code violations (code_violations table) API endpoints: POST /api/repos/:id/violations/:violationId/dismiss — dismiss an architecture violation POST /api/repos/:id/code-violations/:violationId/dismiss — dismiss a code violation Optional: accept a reason field (e.g., "false positive", "accepted risk", "by design") Dismissed violations should persist across analyses — when a violation is carried forward as unchanged, check if the previous version was dismissed and carry the dismissal forward Lifecycle handling: Dismissed violations should NOT appear in the default violations list (filter status IN ('new', 'unchanged') already excludes them
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 truecourse-ai/truecourse, 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 truecourse-ai/truecourse acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 75.3% were successfully merged into the primary branch.
truecourse-ai/truecourse has a recorded first-timer success rate of 33.3%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. 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 66.7 places truecourse-ai/truecourse in the Welcoming tier.
The external pull request merge rate is 75.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, truecourse-ai/truecourse 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 truecourse-ai/truecourse 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.