The Tangent monorepo.
C-Rank Grade: A (Welcoming) - 62/100
External PR Merge Rate: 64%
Response Time: -
First Timer Success: 50%
suchnsuch/Tangent has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in suchnsuch/Tangent 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.
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.0 places suchnsuch/Tangent in the A tier.
The external contributor pull request merge rate for suchnsuch/Tangent is 64.3%, based on public PR activity from non-core contributors.
suchnsuch/Tangent currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in suchnsuch/Tangent. Prompt code reviews with positive guidance for new contributors.
Discussions in suchnsuch/Tangent 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/suchnsuch/Tangent?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 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (80% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
This tool is amazing. I fall in love with it almost everyday... My other issue is my need for line numbering and relative line numbering. This is almost necessary for me when taking notes. I am hoping a setting could be added to allow this. Thank you. P.S. Although this could be an issue of its own, but following the line numbering, is it possible to have VIM keybindings too. This is not a do or die because Tangent is amazing as is.
The idea would be to have an on-screen toggle that would allow or prevent editing for each note. This setting would behave independently for each note. This toggle setting would be especially useful for notes that have been completed, where editing is less important than the preservation and integrity of the existing data. Toggling off edits would prevent editing of data, while preserving the intended behavior of hyperlinks, back-links, tags, media, text, etc. Creating a new note would always default the edit lock toggle to allow changes.
Hi pressing down key (🔽) does not go to the next line when cursor is in a inline math node Rec.0004.mp4 test case ## Question Show that if $x$ is in both $W$ and $W^\perp$, then $x=0$ >pressing key `🔽` does make cursor to go next line version: Tangent 0.12.0-alpha-2 OS: Windows 10
Hello again, Taylor! I hope you're well. It would appear as if spell check isn't flagging words on my end since updating. Thanks!
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 suchnsuch/Tangent, 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 suchnsuch/Tangent acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 64.3% were successfully merged into the primary branch.
suchnsuch/Tangent has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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.0 places suchnsuch/Tangent in the Welcoming tier.
The external pull request merge rate is 64.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, suchnsuch/Tangent currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for suchnsuch/Tangent 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.