Tree Style Tab, Show tabs like a tree.
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 90%
Response Time: 23h
First Timer Success: 100%
piroor/treestyletab has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in piroor/treestyletab respond to incoming external pull requests in approximately 23.4 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.6 places piroor/treestyletab in the A tier.
The external contributor pull request merge rate for piroor/treestyletab is 90.0%, based on public PR activity from non-core contributors.
piroor/treestyletab currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in piroor/treestyletab. Prompt code reviews with positive guidance for new contributors.
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/piroor/treestyletab?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 Tuesday - Thursday 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 ~15 hours (96% approval). Large PRs (>500 lines) take ~112 hours (40% 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 JavaScript.
Serve Swagger-UI for Fastify
Local macOS bridge between ChatGPT Voice and Google Meet
Swagger Editor
Abstract Steps to reproduce Start Firefox with clean profile Install TST Size the current window to full height vertically (but not "maximised", just a normal window at full height) Open a few tabs Using the TST context menu, move a tab to a new window Expected result The new window should also be full height as well, or at least it should not extend off screen. When using Firefox's native tab context menu to move to new window, the new window matches my expectations: it is full height (just like the original window) without extending off screen. Actual result The new window created by TST extends off screen a small amount. So far, I have only tested my current OS (Linux), so this might be platform specific behaviour. I wonder if it's related to TST adding 20 to the new window's top and left...? Curiously though, the new TST-opened window seems to be wider on both the left and right sides. The top edge remains at the top of the screen like the original window, but the bottom edge ext
Steps to reproduce I'm not sure how to reproduce it on a clean profile. When you haven't restarted the browser for several days, and have dozens of tabs active and several hundreds of tabs in total, spreaded in several windows, it could manifest. Expected result Moving tabs around should be smooth and finish instantly. Actual result It becomes very laggy and feels hard to get the tab to the right position I want it to be, because it can't follow the mouse when I'm dragging it. It can take tens of seconds to accomplish a move. Environment I recorded a profile file: Firefox 2026-06-27 04.14 profile.json.gz. From the profile, I can't figure out what's wrong. There seems to be messages flooding, causing CPU to be 100% busy.
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 piroor/treestyletab, 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 piroor/treestyletab acknowledge new external contributions in approximately 23 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 90.0% were successfully merged into the primary branch.
piroor/treestyletab has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~23 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 62.6 places piroor/treestyletab in the Welcoming tier.
The external pull request merge rate is 90.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, piroor/treestyletab currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for piroor/treestyletab 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.