A collection of .NET libraries for rendering mathematical formulae using the LaTeX typesetting style, for the WPF and Avalonia XAML-based frameworks
C-Rank Grade: B (Solid) - 51/100
External PR Merge Rate: 67%
Response Time: <1h
First Timer Success: 100%
ForNeVeR/xaml-math has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ForNeVeR/xaml-math 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 51.4 places ForNeVeR/xaml-math in the B tier.
The external contributor pull request merge rate for ForNeVeR/xaml-math is 66.7%, based on public PR activity from non-core contributors.
ForNeVeR/xaml-math currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in ForNeVeR/xaml-math welcoming community pull requests and bug fixes.
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/ForNeVeR/xaml-math?utm_source=github&utm_medium=badge)
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 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 10:00 to 14:00 UTC (10:00 - 14:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (83% approval). Large PRs (>500 lines) take ~0 hours (30% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in C#.
DeepSeek API SDK for .NET developer
Multi-player MS Paint application. Built with Akka.NET, Blazor, and .NET Aspire.
.NET (WPF and Windows Forms) bindings for the Chromium Embedded Framework
The constructors of its base class Box and some other derived classes like CharBox require a argument of type TexEnvironment, from which they initialize their Foreground property. But the constructor of StrokeBox does not accept arguments of type TexEnvironment, which makes its Foreground property not set in constructor and stay null. As a result, if FormulaControl.Foreground is set to other color, the color of lines rendered from StrokeBox is still the fallback value set in IElementRenderer.RenderLine. I think we can add a parameter of type TexEnvironment to the constructor of StrokeBox. The constructor is only used in CancelAtom.CreateBoxCore method. public StrokeBox(TexEnvironment environment, StrokeBoxMode mode) : base(environment) { _mode = mode; } protected override Box CreateBoxCore(TexEnvironment environment) { var contentBox = _contentAtom is null ? StrutBox.Empty : _contentAtom.CreateBox(environment); var lineBox = new StrokeBox(environment, _strokeBoxMode) {
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 ForNeVeR/xaml-math, 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 ForNeVeR/xaml-math acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 66.7% were successfully merged into the primary branch.
ForNeVeR/xaml-math has a recorded first-timer success rate of 100.0%. Repositories ranked Solid 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 51.4 places ForNeVeR/xaml-math in the Solid tier.
The external pull request merge rate is 66.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ForNeVeR/xaml-math 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 ForNeVeR/xaml-math 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.