A shell auto-completion tool for your terminal
C-Rank Grade: S (Elite) - 77/100
External PR Merge Rate: 93%
Response Time: 2d
First Timer Success: 83%
versenilvis/IRIS has a recorded first-timer success rate of 83.3%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in versenilvis/IRIS respond to incoming external pull requests in approximately 44.5 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.3 places versenilvis/IRIS in the S tier.
The external contributor pull request merge rate for versenilvis/IRIS is 93.5%, based on public PR activity from non-core contributors.
versenilvis/IRIS currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in versenilvis/IRIS. 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/versenilvis/IRIS?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 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 09:00 to 13:00 UTC (09:00 - 13: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 ~29 hours (96% approval). Large PRs (>500 lines) take ~214 hours (42% 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 Go.
[Go]Distributed Actor/Grain framework for Golang with goodies
Every API has a secret identity. This finds it, absorbs every feature from every competing tool, then builds the GOAT CLI — designed for AI agents first, with SQLite sync, offline search, and compound insight commands.
No repository description available.
Describe the feature Sync the IRIS theme with the Omarchy shell theme. Changing the Omarchy shell theme will too change IRIS theme, maintaining the system visually esthetics. It should be implemented because Omarchy is a Linux distro that's trending (19° position at DistroWatch) and is getting a huge hype from the community. Additional context No response Would you like to work on this issue? None
Describe your issue When IRIS is installed, the cosmic-launcher (user login screen) is not able to start the cosmic-session (desktop environment). Instead it falls into the terminal interface where IRIS is working. You can start the cosmic-session manually from there, but it is not correctly initialized. IRIS is not working in the manually started cosmic de session. Steps to reproduce Have an PopOS with Cosmic Desktop Install IRIS Reboot What was the expected result? IRIS does not affect the Cosmic Desktop startup process. Put here any screenshots or videos (optional) No response Your OS and Browser (optional) OS: PopOS 24.04 DE: Cosmic Epoch 1.5.0
Describe the feature Native nushell support — iris init nu, a real nu adapter, the whole thing. Right now IRIS only does bash/zsh/fish. My login shell is nu (/opt/homebrew/bin/nu), and core.shell rejects anything outside bash|zsh|fish. Workaround is launching iris with -s fish/-s zsh, but then you're not actually in nu anymore (different syntax, history, completions). Not really usable as a daily driver if nu is your shell. It should be implemented because A bunch of people already live in nushell full-time. Without a nu adapter, iris just isn't an option unless you bounce into another shell, which kinda defeats the point. Additional context Nushell: https://github.com/nushell/nushell Looks like the shell adapters live under integration/shell (Bash/Zsh/Fish). Nu would need the same kind of thing: spawn nu in the PTY, wire cwd/cmd start-stop hooks, and whatever line-buffer sync makes sense for nu's reedline. History side: nu can use sqlite history ($env.config.history.file_format = "
IRIS has to handle commands manually, and so many commands I haven't added yet Need your help
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 versenilvis/IRIS, 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 versenilvis/IRIS acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 93.5% were successfully merged into the primary branch.
versenilvis/IRIS has a recorded first-timer success rate of 83.3%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. 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.3 places versenilvis/IRIS in the Elite tier.
The external pull request merge rate is 93.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, versenilvis/IRIS currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for versenilvis/IRIS 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.