LL(k) and LALR(1) parser generator for Rust and C#
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 97%
Response Time: <1h
First Timer Success: 100%
jsinger67/parol has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in jsinger67/parol 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 65.9 places jsinger67/parol in the A tier.
The external contributor pull request merge rate for jsinger67/parol is 97.2%, based on public PR activity from non-core contributors.
jsinger67/parol currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Responsive & active maintainer team in jsinger67/parol. Reviews pull requests with focus on project architectural goals.
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/jsinger67/parol?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~0 hours (44% approval). Keep your diff compact for rapid review.
Summary The Par grammar already has language server support in this repository, but editor integration outside VS Code can be improved and made easier to adopt. This issue tracks support and documentation for using the Par language server in other popular editors (for example Neovim, Helix, Emacs, Sublime Text, and JetBrains via LSP plugins). Why this matters More users can adopt Par from their preferred editor. Better LSP coverage improves discoverability and developer experience. This is a good contribution area for community members who want to help with practical, user-facing improvements. Scope Provide setup guides for common editors using standard LSP clients/plugins. Validate basic language features in each editor: Diagnostics Go to definition Hover Completion (if available) Formatting support (if available) Document known limitations and editor-specific workarounds. Add minimal test/verification instructions so others can reproduce setup. Proposed deliverables A docs pa
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 jsinger67/parol, 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 jsinger67/parol acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 97.2% were successfully merged into the primary branch.
jsinger67/parol has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. 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 65.9 places jsinger67/parol in the Welcoming tier.
The external pull request merge rate is 97.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, jsinger67/parol currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for jsinger67/parol 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.