A Universal TUI Manual Viewer for CLI Tools in Rust
C-Rank Grade: S (Elite) - 71/100
External PR Merge Rate: 88%
Response Time: 5h
First Timer Success: 67%
AS-FOSS/mandible 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.
Maintainers in AS-FOSS/mandible respond to incoming external pull requests in approximately 5.2 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 71.0 places AS-FOSS/mandible in the S tier.
The external contributor pull request merge rate for AS-FOSS/mandible is 88.4%, based on public PR activity from non-core contributors.
AS-FOSS/mandible does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Collaborative maintainer environment in AS-FOSS/mandible. Reviews community pull requests with focus on project quality.
Discussions in AS-FOSS/mandible 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/AS-FOSS/mandible?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 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 21:00 to 01:00 UTC (21:00 - 01:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~25 hours (40% approval). Keep your diff compact for rapid review.
In mandible icupkg the flag list shows -c or with no description. The row is -c or --copyright include the ICU copyright notice Two value-free spellings joined by the word or, with the description starting one space after --copyright. The parser already reads or-joined rows when they carry values or when the description sits two or more spaces away (docs/shapes.md S-099). This value-free, one-space form is the gap: -c keeps the literal word or as its value name, --copyright reaches nothing. What it should look like: one flag with spellings -c, --copyright and the description include the ICU copyright notice, exactly like the row below it, -C comment or --comment comment, already renders. Where to read docs/shapes.md S-134 (this shape) and S-099 (the or-joined rule that exists). corpus/icupkg/74.2/meta.toml, the fixture, marked [xfail] with this shape in the reason. xtask/src/detector/or_joined_alias_single_space_gap.rs, the fleet detector, and its self-check cases: they show what mu
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 AS-FOSS/mandible, 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 AS-FOSS/mandible acknowledge new external contributions in approximately 5 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 88.4% were successfully merged into the primary branch.
AS-FOSS/mandible 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.
The initial maintainer response time averages ~5 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 71.0 places AS-FOSS/mandible in the Elite tier.
The external pull request merge rate is 88.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
AS-FOSS/mandible does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for AS-FOSS/mandible 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.