A good looking terminal emulator which mimics the old cathode display...
C-Rank Grade: D (Risky) - 16/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
Swordfish90/cool-retro-term has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Swordfish90/cool-retro-term 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 16.4 places Swordfish90/cool-retro-term in the D tier.
The external contributor pull request merge rate for Swordfish90/cool-retro-term is 0.0%, based on public PR activity from non-core contributors.
Swordfish90/cool-retro-term currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in Swordfish90/cool-retro-term. Reviews community pull requests with focus on project quality.
Discussions in Swordfish90/cool-retro-term 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/Swordfish90/cool-retro-term?utm_source=github&utm_medium=badge)
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 01:00 UTC (01:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
the command line switch --fullscreen stopped working after a recent update. previously, running $ cool-retro-term --fullscreen … opened a full screen terminal, but now it opens a windowed terminal. i had this command bound to a shortcut for ‘instant hacker vibes’ 🤓 , but now that it stopped working i cannot show off anymore when someone walks past my desk 😿
"Burn In" is not burn in. "Burn In" is phosphor persistence. Actual burn-in is a completely different phenomenon where the phosphors become physically damaged over time when exposed to a constant static image. https://en.wikipedia.org/wiki/Screen_burn-in
First off, I am absolutely loving the recent work you've been doing on CRT. It's really coming together nicely. I have one big problem with this new version though: profiles. In the old version each instance of CRT ran in its own process, and different profiles could be chosen for each process. That was great, as I could have different looking screens for different servers I was connected to, and could instantly know which computer I was typing into. Now all CRTs run in the same process. Changing the profile on one window instantly changes it on all other windows. Even when manually starting a new process from the command line and specifying the profile to use it just attaches to the existing process and spawns a new window. I really need either that old process separation to keep everything separate, or a way of specifying per window what profile it should be using. Also, I am getting some semi-random crashes when opening multiple windows, changing profile, then closing one window - w
Summary When opening more than 2 terminals in the same desktop they all crash. When closing an existing terminal all the other cool-retro-term terminals crash. When switching focus between windows in i3 I briefly toggle borders via a small script so the focused window is obvious. If either the window losing focus or gaining focus is cool-retro-term, both cool-retro-term windows crash immediately when the border change is applied. Environment i3 window manager (X11) cool-retro-term 2.0.0-beta1 AppImage OS: Arch Linux (X11) Notes Other terminal emulators (only tested in alacritty) do not crash in any of these actions. The closing problem only occurs if I close it using the key binding (configured in the /.config/i3/config) file or if I close a tab manually. When closing it with the exit command it works correctly.
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 Swordfish90/cool-retro-term, 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 Swordfish90/cool-retro-term acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
Swordfish90/cool-retro-term has a recorded first-timer success rate of 0.0%. Repositories ranked Risky 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 16.4 places Swordfish90/cool-retro-term in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Swordfish90/cool-retro-term 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 Swordfish90/cool-retro-term 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.