A programming language supporting most features of both declarative and imperative languages
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 79%
Response Time: 2h
First Timer Success: 67%
pschachte/wybe has a recorded first-timer success rate of 66.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in pschachte/wybe respond to incoming external pull requests in approximately 1.8 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 64.4 places pschachte/wybe in the A tier.
The external contributor pull request merge rate for pschachte/wybe is 78.9%, based on public PR activity from non-core contributors.
pschachte/wybe currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in pschachte/wybe. Prompt code reviews with positive guidance for new contributors.
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/pschachte/wybe?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 04:00 UTC (04:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~9 hours (36% approval). Keep your diff compact for rapid review.
Currently, names produced in generated LLVM code are not consistently mangled to ensure they don't clash with one another or with user-written code. We should think through how much mangling is needed for this, and implement it consistently for all generated names in LLVM code.
It would be good if the compiler can give warnings on unused variable declarations. In the following example, the x variable is unused: def foo { ?x = 42 } This should help reduce the occurrence of issues like #560.
There appears to be a typo on line 100 of list.wybe, which is causing the procedure to not work as expected. pub def filter(p:{test}(T), !xs:_(T)) { ?out = [] for ?x in xs { if { p(x) :: ?out = [x | out] } } ?as = reverse(out) # should be `xs` }
Currently, the interface for lpvm mutate looks like this: foreign lpvm mutate(struct:type, ?struct2:type, offset:int, destructive:bool, size:int, start_offset:int, member:type2) It is common to have struct and struct2 named the same. I propose we add a variant for this proc that allows for ! on the first argument foreign lpvm mutate( !struct:type, offset:int, destructive:bool, size:int, start_offset:int, member:type2) which has the same semantics as the former except that ?struct2 = struct after the call. We can trivially eliminate this variant in the flattening stage.
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 pschachte/wybe, 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 pschachte/wybe acknowledge new external contributions in approximately 1 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 78.9% were successfully merged into the primary branch.
pschachte/wybe has a recorded first-timer success rate of 66.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 64.4 places pschachte/wybe in the Welcoming tier.
The external pull request merge rate is 78.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, pschachte/wybe currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for pschachte/wybe 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.