MathCAT: Math Capable Assistive Technology for generating speech, braille, and navigation.
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 59%
Response Time: 2d
First Timer Success: 50%
daisy/MathCAT has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in daisy/MathCAT respond to incoming external pull requests in approximately 41.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 59.0 places daisy/MathCAT in the A tier.
The external contributor pull request merge rate for daisy/MathCAT is 58.8%, based on public PR activity from non-core contributors.
daisy/MathCAT currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Rust project in daisy/MathCAT 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/daisy/MathCAT?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 ~27 hours (74% approval). Large PRs (>500 lines) take ~201 hours (26% approval). Keep your diff compact for rapid review.
in cargo.toml, the [[package]] block still contains: repository = "https://github.com/NSoiffer/MathCAT" homepage = "https://nsoiffer.github.io/MathCAT/" documentation = "https://nsoiffer.github.io/MathCAT/" this should be replaced with the respective DAISY URLs. Open question: which other places also need some cleanup like this?
The logo needs to be added/designed for the following (sub) document pages: AT users: information about preferences you can set AT developers/library users: information about the API that MathCAT exposes Translators/Rule writers: information about the files that need to be translated MathCAT developers: information about development workflow and testing Note: this is not #406.: the logo exists but it is either not present or not really designed properly for these pages.
In some area, people use $\overset{\rightharpoonup}{OA}$ to denote a vector from point O to point A. In all area, people use $\overline{OA}$ to denote a line segment from point O to point A. In Intent/geometry.yaml, there is already a rule geometry-line-segment(mover) for line segment: - name: geometry-line-segment tag: mover match: - "*[2][self::m:mo][.='¯'] and" - "*[1][self::m:mrow][count(*)=3 and " - " *[1][self::m:mi and string-length(text()) and translate(., 'ABCDEFGHIJKLMNOPQRSTUVWXYZ', '') = ''] and" - " *[2][self::m:mo and (.='\u2062' or .='\u2063')] and" - " *[3][self::m:mi and string-length(text()) and translate(., 'ABCDEFGHIJKLMNOPQRSTUVWXYZ', '') = '']" - " ]" replace: - intent: name: "line-segment" attrs: "data-intent-property='concat(data-intent-property, \":prefix:\")'" children: - x: "*[1]/*[1]" - x: "*[1]/*[3]" hope MathCAT can add new rule geometry-harpoonvector(mover) for
As reported by @jrbowden ICEB has published some updated guidelines on choice and placement of grade 1 indicators. This guidance brings more consistency in the way mathematical expressions are rendered in UEB. You can find the document at https://iceb.org/publications/ueb/ under the heading Revisions to Guidelines for Technical Material.
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 daisy/MathCAT, 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 daisy/MathCAT acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 58.8% were successfully merged into the primary branch.
daisy/MathCAT has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. 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 59.0 places daisy/MathCAT in the Welcoming tier.
The external pull request merge rate is 58.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, daisy/MathCAT currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for daisy/MathCAT 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.