A simple, yet effective Personal Relationship Manager
C-Rank Grade: S (Elite) - 77/100
External PR Merge Rate: 92%
Response Time: 5h
First Timer Success: 60%
mattogodoy/nametag has a recorded first-timer success rate of 60.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in mattogodoy/nametag respond to incoming external pull requests in approximately 4.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 77.4 places mattogodoy/nametag in the S tier.
The external contributor pull request merge rate for mattogodoy/nametag is 91.6%, based on public PR activity from non-core contributors.
mattogodoy/nametag currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
A simple, yet effective Personal Relationship Manager
Strict review standards in mattogodoy/nametag. 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/mattogodoy/nametag?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 18:00 UTC (18:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 16:00 to 20:00 UTC (16:00 - 20:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~23 hours (41% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in TypeScript.
ZoneMinder client for iOS, Android, Windows, macOS, Linux and web. Live camera view, event review, montage, timeline, push notifications. Rewrite of zmNinja.
No repository description available.
Open-source, self-hosted file-processing tool. Convert, compress, OCR, transcribe & run local AI across image, video, audio, PDF & documents, via UI, REST API & pipelines. Your files never leave your network.
createNtfyEndpointSchema in lib/validations.ts is now a @deprecated alias kept solely so that existing tests resolve. The creation route validates with createEndpointSchema, the discriminated union that also accepts webhooks. The two are structurally equivalent today, because the union contains exactly that object, so nothing is actually untested. But tests/lib/validations.test.ts exercises a schema that no production code path uses, which is the kind of divergence that quietly stops meaning anything the moment the union changes. Point those tests at createEndpointSchema and delete the alias. While there, note that createEndpointSchema itself has no direct unit tests in that file, so the union's discriminant behaviour is only covered indirectly through the route tests. Found during review of #449.
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 mattogodoy/nametag, 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 mattogodoy/nametag acknowledge new external contributions in approximately 4 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 91.6% were successfully merged into the primary branch.
mattogodoy/nametag has a recorded first-timer success rate of 60.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~4 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 77.4 places mattogodoy/nametag in the Elite tier.
The external pull request merge rate is 91.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, mattogodoy/nametag 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 mattogodoy/nametag 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.