neurosnap/zmx - Open Source PR Review Scorecard

Session attach/detach for the terminal

C-Rank Grade: B (Solid) - 48/100

External PR Merge Rate: 46%

Response Time: 2d

First Timer Success: 33%

Frequently Asked Questions

Is neurosnap/zmx welcoming to first-time open-source contributors?

neurosnap/zmx has a recorded first-timer success rate of 33.3%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in neurosnap/zmx respond to incoming external pull requests in approximately 41.2 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 47.6 C-Rank™ score (B Tier) represent?

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 47.6 places neurosnap/zmx in the B tier.

What is the external contributor pull request merge rate for neurosnap/zmx?

The external contributor pull request merge rate for neurosnap/zmx is 46.4%, based on public PR activity from non-core contributors.

Are there Good First Issues available in neurosnap/zmx?

neurosnap/zmx currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

neurosnap
neurosnap/zmxBSolid2.1k
GitHub
Back to Explorer
neurosnap

neurosnap/zmx

2,059
BSolid(48/100)Zig

Session attach/detach for the terminal

Compare
Jump to:
Response Velocity
1 days+
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
46.4%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
33.3%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
29 core
Highly collaborative maintainer core
Diagnostic Health HUD
46.4%
Merge Gauge
33.3%
1st-Timer
Community Vibe29/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for neurosnap/zmx
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/neurosnap/zmx)](https://getmerged.abhishekco.de/neurosnap/zmx?utm_source=github&utm_medium=badge)

Active Good First Issues (1)

View on GitHub

Not sure if this is planned for this minimalist tool, so this is more of an inquiry/suggestion than an issue. We had a server OOM yesterday and had to force reboot the machine. All zmx sessions were gone after the restart, including the metadata (session names, creation time, start directory, etc.). I used to manage background sessions with zellij and it would retain the metadata but often lose previous session outputs (which is fine). Do you think it would be possible to persist some or all of the session data on crashes? Thanks again for the tool! Been really amazing so far.

📅 Opened Mar 6, 2026💬 10 comments
Quality: 70/100Contribute
Looking for more Zig beginner tasks?Explore Zig GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for neurosnap/zmx

When evaluating whether to contribute to neurosnap/zmx, 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 neurosnap/zmx acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 46.4% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to neurosnap/zmx

01

Is neurosnap/zmx welcoming to first-time open-source contributors?

neurosnap/zmx has a recorded first-timer success rate of 33.3%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~1 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 47.6 C-Rank™ score represent?

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 47.6 places neurosnap/zmx in the Solid tier.

04

What is the external contributor pull request merge rate for neurosnap/zmx?

The external pull request merge rate is 46.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in neurosnap/zmx?

Yes, neurosnap/zmx currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for neurosnap/zmx 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.