here-Leslie-Lau/zlist - Open Source PR Review Scorecard

A modern ls alternative written in Zig.

C-Rank Grade: S (Elite) - 73/100

External PR Merge Rate: 94%

Response Time: 3h

First Timer Success: 67%

Frequently Asked Questions

Is here-Leslie-Lau/zlist welcoming to first-time open-source contributors?

here-Leslie-Lau/zlist has a recorded first-timer success rate of 66.7%. Repositories ranked S 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 here-Leslie-Lau/zlist respond to incoming external pull requests in approximately 3.2 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 73.1 C-Rank™ score (S 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 73.1 places here-Leslie-Lau/zlist in the S tier.

What is the external contributor pull request merge rate for here-Leslie-Lau/zlist?

The external contributor pull request merge rate for here-Leslie-Lau/zlist is 93.9%, based on public PR activity from non-core contributors.

Are there Good First Issues available in here-Leslie-Lau/zlist?

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

here-Leslie-Lau
here-Leslie-Lau/zlistSElite56
GitHub
Back to Explorer
here-Leslie-Lau

here-Leslie-Lau/zlist

56
SElite(73/100)Zig

A modern ls alternative written in Zig.

Compare
Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score
9.0/10
Patience Score
8.8/10
Nitpick Rate
35%

Highly welcoming maintainers in here-Leslie-Lau/zlist. Prompt code reviews with positive guidance for new contributors.

Top PR Submission Do's

  • Ensure code complies with the project coding style
  • Keep PRs scoped to a single concern
  • Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • Do not submit PRs without linking an issue
  • Do not break existing tests without fixing them
  • Do not mix unrelated refactors in a single PR
Response Velocity
3 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
93.9%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
66.7%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
2 core
Small core review team
Diagnostic Health HUD
93.9%
Merge Gauge
66.7%
1st-Timer
Community Vibe85/100

Embed C-Rank Badge

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

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

Active Good First Issues (1)

View on GitHub

eza has hyprlink support, which makes all the entries clickable. It's not something I personally use, but I could see someone else liking it. I would honestly not be interested in implementing this one as I don't need it, but might as well make a feature request.

📅 Opened Jul 30, 2026💬 1 comment
Quality: 75/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 here-Leslie-Lau/zlist

When evaluating whether to contribute to here-Leslie-Lau/zlist, 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 here-Leslie-Lau/zlist acknowledge new external contributions in approximately 3 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 93.9% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to here-Leslie-Lau/zlist

01

Is here-Leslie-Lau/zlist welcoming to first-time open-source contributors?

here-Leslie-Lau/zlist has a recorded first-timer success rate of 66.7%. Repositories ranked Elite 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 ~3 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 73.1 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 73.1 places here-Leslie-Lau/zlist in the Elite tier.

04

What is the external contributor pull request merge rate for here-Leslie-Lau/zlist?

The external pull request merge rate is 93.9%. 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 here-Leslie-Lau/zlist?

Yes, here-Leslie-Lau/zlist 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 here-Leslie-Lau/zlist 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.