Submitty/Submitty - Open Source PR Review Scorecard

Homework Submission, Automated Grading, and TA grading system.

C-Rank Grade: S (Elite) - 70/100

External PR Merge Rate: 67%

Response Time: -

First Timer Success: 70%

Frequently Asked Questions

Is Submitty/Submitty welcoming to first-time open-source contributors?

Submitty/Submitty has a recorded first-timer success rate of 69.6%. Repositories ranked S 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 Submitty/Submitty 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 70.4 C-Rank™ score (S 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 70.4 places Submitty/Submitty in the S tier.

What is the external contributor pull request merge rate for Submitty/Submitty?

The external contributor pull request merge rate for Submitty/Submitty is 67.3%, based on public PR activity from non-core contributors.

Are there Good First Issues available in Submitty/Submitty?

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

Submitty
Submitty/SubmittyS•Elite802
GitHub
Back to Explorer
Submitty

Submitty/Submitty

802
Active (30d)S•Elite(70/100)PHP

Homework Submission, Automated Grading, and TA grading system.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Strict Quality Architect

Warmth Score
6.9/10
Patience Score
7.4/10
Nitpick Rate
39%

Balanced & professional review environment in Submitty/Submitty. 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
67.3%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
69.6%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
37 core
Highly collaborative maintainer core
Diagnostic Health HUD
67.3%
Merge Gauge
69.6%
1st-Timer
Community Vibe48/100

Embed C-Rank Badge

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

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

Active Good First Issues (5)

View on GitHub

What problem are you trying to solve with Submitty Universities and Instructors like to keep in contact with students after graduation. Students build resumes/portfolios/work histories on popular websites. Let's give students the option to share links to these materials through Submitty. Describe the way you'd like to solve this problem The master database for Submitty already has an optional field "secondary email". This field is sync-ed through a trigger function to each course database the student is part of. Let's add a few additional fields to the master & course database with the same trigger function mechanism: linkedin_username github_username personal_webpage The student's profile page should be expanded to collect these 3 optional fields. We should do some error checking on these fields to make sure they contain only the allowed characters and when constructed into a URL the paths are valid and functional. The text when we collect these fields should make clear that

📅 Opened Oct 14, 2026💬 0 comments
Quality: 90/100Contribute

Describe the bug From the TA grading page of a gradeable with peer grading, clicking on "Statistics & Charts" gives us some information about peer grading completed, but I don't understand it: Yes, I have ~108 students in the course. ~99 of them submitted to this particular assignment Every student who submitted the assignment was assigned (randomly) to peer grade 3 of the other students who had also submitted the assignment. 31 of those students did not do any peer grading. The remaining students did most or all of their peer grading (I don't have an exact count, but only a handful graded 1 or 2 students -- this only happened if one of their assigned students left that part of the assignment blank). I would expect to see ~68/~99 as the percentage of peer grading completed. I'm not sure where the numbers "60" and "84" come from. NOTE: I use '~' in the above numbers because I have my own test student account in the course and there are possibly a couple special case students (late

📅 Opened Oct 13, 2026💬 0 comments
Quality: 90/100Contribute

Describe the bug Followup to PR #13467. The summary & individual tabs of peer grading is inconsistent and a bit confusing. The summary does not make clear why I received 1.5 / 2 for peer grading. It looks like I should get 1.5+0.5 = 2.0. The one peer that graded me clicked 1.5. (So the overall grade is correct... but its confusing!) Why does the summary just show 2 marks and the individual shows all of the marks? Those 2 marks are labeled "show mark to all students" Expected behavior The marks selected by each individual should be displayed like the marks from non-peer graders. Marks that are not selected and are not labeled "show mark to all students" should not be included in the list. The summary table needs to be revised as well. It's probably confusing when the scores are averaged across multiple users...

📅 Opened Oct 13, 2026💬 0 comments
Quality: 90/100Contribute

Describe the bug As an instructor, with a staff of TAs assigned to do the bulk of grading, the first time I open the TA grading index page for a gradeable, I always see "Only Assigned Sections" checked. This blocks me from viewing the class and I always uncheck "Only assigned sections". In the future when I return to this gradeable, that option is unchecked. Expected behavior The cookie or local storage we are using to store the user's selection that option is too specific. I believe for most users, the selection to view all sections should be sticky across every gradeable I open in this course, and arguably for it should also be sticky across every course I visit on Submitty. NOTE: We should also revisit the defaults & stored selections for the other options on the TA grading page. We should have a clear decision for which should be global / per course / per gradeable. ALSO: Any PR to address this should make sure we have a clear naming convention for these settings and do approp

📅 Opened Oct 12, 2026💬 3 comments
Quality: 90/100Contribute

What problem are you trying to solve with Submitty I am an instructor and I receive an email that a post has been made to a grade inquiry thread, but there is no link to the specific gradeable + student if I want to review the materials and contribute to the discussion Describe the way you'd like to solve this problem Let's add a link to the grade inquiry emails & notifications. If I'm a student and there is activity on my grade inquiry, the link should be to the submission page for that gradeable. If I'm a full access grader or instructor, the link should be to the TA grading page for that gradeable and to the specific student. NOTE: Currently the email does not include the name of the student nor the name of the grader. Let's keep it that way. The link to the specific students assignment should also not include the name of the student but should use the anonymous id. (The name of the student should not be in the email in any way.)

📅 Opened Oct 10, 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 Submitty/Submitty

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

Frequently Asked Questions - Contributing to Submitty/Submitty

01

Is Submitty/Submitty welcoming to first-time open-source contributors?

Submitty/Submitty has a recorded first-timer success rate of 69.6%. Repositories ranked Elite 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 70.4 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 70.4 places Submitty/Submitty in the Elite tier.

04

What is the external contributor pull request merge rate for Submitty/Submitty?

The external pull request merge rate is 67.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 Submitty/Submitty?

Yes, Submitty/Submitty currently has 37 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 Submitty/Submitty 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.

Submitty/Submitty • 70.4/100 C-Rank (S-Tier) | GetMerged