TLC is a model checker for specifications written in TLA+. The TLA+Toolbox is an IDE for TLA+.
C-Rank Grade: A (Welcoming) - 62/100
External PR Merge Rate: 63%
Response Time: 14h
First Timer Success: 25%
tlaplus/tlaplus has a recorded first-timer success rate of 25.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in tlaplus/tlaplus respond to incoming external pull requests in approximately 14.1 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 62.3 places tlaplus/tlaplus in the A tier.
The external contributor pull request merge rate for tlaplus/tlaplus is 62.9%, based on public PR activity from non-core contributors.
tlaplus/tlaplus currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (100% critical review signals). Ensure PRs strictly follow guidelines before requesting review in tlaplus/tlaplus.
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/tlaplus/tlaplus?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 ~9 hours (79% approval). Large PRs (>500 lines) take ~68 hours (28% approval). Keep your diff compact for rapid review.
The output produced by XMLExporter contains a complete representation of the AST, including every element. Each element is self-contained, which results in substantial duplication of information. While this verbosity is acceptable—and often desirable—when the output is consumed by deterministic tools such as IDEs or proof assistants, it becomes problematic in LLM-based chat settings, where the available token budget is limited. To address this issue, the TLA+ VSCode/Cursor extension applies significant filtering and compression to XMLExporter’s output before converting it to JSON and passing it to LLMs (see tlaplus/vscode-tlaplus#448). Selective Extraction (Skipping) The tool parses SANY's full XML output but only extracts specific top-level declarations: UserDefinedOpKind - User-defined operators TheoremDefNode - Theorems, axioms, lemmas AssumeDef - Assumptions OpDeclNode - Variables and constants It completely skips: The full abstract syntax tree (AST) for expressions Nested
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 tlaplus/tlaplus, 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 tlaplus/tlaplus acknowledge new external contributions in approximately 14 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 62.9% were successfully merged into the primary branch.
tlaplus/tlaplus has a recorded first-timer success rate of 25.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~14 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 62.3 places tlaplus/tlaplus in the Welcoming tier.
The external pull request merge rate is 62.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, tlaplus/tlaplus 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 tlaplus/tlaplus 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.