TEAMMATES is a feedback management tool for education
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 81%
Response Time: 4d
First Timer Success: 53%
TEAMMATES/teammates has a recorded first-timer success rate of 53.1%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in TEAMMATES/teammates respond to incoming external pull requests in approximately 85.8 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 62.9 places TEAMMATES/teammates in the A tier.
The external contributor pull request merge rate for TEAMMATES/teammates is 81.0%, based on public PR activity from non-core contributors.
TEAMMATES/teammates currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (66% critical review signals). Ensure PRs strictly follow guidelines before requesting review in TEAMMATES/teammates.
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/TEAMMATES/teammates?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 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 23:00 to 03:00 UTC (23:00 - 03:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~56 hours (96% approval). Large PRs (>500 lines) take ~412 hours (36% approval). Keep your diff compact for rapid review.
The back-end action and servlet layers either use hard-coded param key values or import from Const.ParamsNames. However, the front-end components all have hard-coded param keys. This increases the risk of mismatched parameter names and inconsistencies between the front and back-end. We should replace hard-coded param keys to Const.ParamsNames and expose those that are shared with front-end components (i.e. methods that prepare paramsMap before calling the API endpoint) in api-const.ts
The current UI for reminding specific students and instructors who have not submitted is implemented as a modal. While this works for small classes, it does not scale well when there are a large number of students and instructors. The modal becomes excessively long, requiring significant scrolling to locate and select recipients. This makes the workflow cumbersome and increases the likelihood of selection errors. Proposed Solution Replace the modal with a dedicated Send Reminders page. See existing Individual Deadline Extensions page for a reference.
Currently, there is no functionality to mark all notifications as read. A button to mark all as read could improve the user experience should there ever be a case where there are a large amount of notifications (e.g. if we introduce notifications for specific course based events in the future).
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 TEAMMATES/teammates, 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 TEAMMATES/teammates acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 81.0% were successfully merged into the primary branch.
TEAMMATES/teammates has a recorded first-timer success rate of 53.1%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 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 62.9 places TEAMMATES/teammates in the Welcoming tier.
The external pull request merge rate is 81.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, TEAMMATES/teammates currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for TEAMMATES/teammates 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.