leanprover-community/physlib - Open Source PR Review Scorecard

A project to digitalise results from physics into Lean.

C-Rank Grade: A (Welcoming) - 59/100

External PR Merge Rate: 6%

Response Time: 7h

First Timer Success: -

Frequently Asked Questions

Is leanprover-community/physlib welcoming to first-time open-source contributors?

leanprover-community/physlib has a recorded first-timer success rate of 0.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in leanprover-community/physlib respond to incoming external pull requests in approximately 6.9 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 59.3 C-Rank™ score (A Tier) represent?

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.3 places leanprover-community/physlib in the A tier.

What is the external contributor pull request merge rate for leanprover-community/physlib?

The external contributor pull request merge rate for leanprover-community/physlib is 6.5%, based on public PR activity from non-core contributors.

Are there Good First Issues available in leanprover-community/physlib?

leanprover-community/physlib currently has 38 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

leanprover-community
leanprover-community/physlibA•Welcoming700
GitHub
Back to Explorer
leanprover-community

leanprover-community/physlib

700
Active (30d)A•Welcoming(59/100)Low Sample (<20 PRs)LELean

A project to digitalise results from physics into Lean.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Maintainer

Warmth Score
7.8/10
Patience Score
8.2/10
Nitpick Rate
20%

Active maintainer team in leanprover-community/physlib welcoming community pull requests and bug fixes.

Top PR Submission Do's

  • •Ensure code complies with repository style conventions
  • •Keep PRs focused and well-documented

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without context
  • •Do not break existing automated test suites
Response Velocity
6 hours
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
6.5%
Selective PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
0.0%
No first-timer merges recorded in window

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
22 core
Highly collaborative maintainer core
Diagnostic Health HUD
6.5%
Merge Gauge
0.0%
1st-Timer
Community Vibe27/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for leanprover-community/physlib
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/leanprover-community/physlib)](https://getmerged.abhishekco.de/leanprover-community/physlib?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

We should add an API-map for Lattice QFT including the main results that we would want to include there.

📅 Opened Aug 31, 2026💬 0 comments
Quality: 75/100Contribute

⚠️ Found by a local LLM, not a human. This was flagged by an automated documentation-mistake finder (qwen3:14b) and passed 10/10 independent verification runs before filing, but it has not been reviewed by a person. Please check it's a genuine error before acting on it. Summary The documentation in Physlib/Relativity/Tensors/Elab.lean (around line 31) is incorrect. Current text Suppose `T2` is a tensor with color `![c3]`. Then `{T | μ ν ⊗ T2 | σ}ᵀ` is `prodNode (tensorNode T1) (tensorNode T2)`. Why this is wrong The documentation example claims that {T | μ ν ⊗ T2 | σ}ᵀ elaborates to prodNode (tensorNode T1) (tensorNode T2). This is incorrect because the preceding sentence introduces T, not T1, as the tensor with color ![c3]. The use of T1 refers to an undefined variable, while T is explicitly mentioned in the context. The correction replaces T1 with T, aligning the example with the declared tensor name. This matches the structure of other examples in the file, whi

📅 Opened Aug 17, 2026💬 0 comments
Quality: 60/100Contribute

⚠️ Found by a local LLM, not a human. This was flagged by an automated documentation-mistake finder (qwen3:14b) and passed 10/10 independent verification runs before filing, but it has not been reviewed by a person. Please check it's a genuine error before acting on it. Summary The documentation in Physlib/QFT/PerturbationTheory/WickAlgebra/WicksTheorem.lean (around line 59) is incorrect. Current text 1. `timeOrder_eq_maxTimeField_mul_finset` is used to write `𝓣(φ₀…φₙ)` as `𝓢(φᵢ,φ₀…φᵢ₋₁) • φᵢ * 𝓣(φ₀…φᵢ₋₁φᵢ₊₁φₙ)` where `φᵢ` is the maximal time field in `φ₀…φₙ` Why this is wrong The documentation for the lemma timeOrder_eq_maxTimeField_mul_finset claims that 𝓣(φ₀…φₙ) is expressed using a term involving 𝓢(φᵢ, φ₀…φᵢ₋₁). This is incorrect because 𝓢 is not defined in the file and does not correspond to any standard notation in quantum field theory. In the context of time-ordered pr

📅 Opened Aug 17, 2026💬 0 comments
Quality: 60/100Contribute

⚠️ Found by a local LLM, not a human. This was flagged by an automated documentation-mistake finder (qwen3:14b) and passed 10/10 independent verification runs before filing, but it has not been reviewed by a person. Please check it's a genuine error before acting on it. Summary The documentation in Physlib/Particles/SuperSymmetry/SU5/ChargeSpectrum/Map.lean (around line 21) is incorrect. Current text There are various properties which are preserved under this mapping: - Anomaly cancellation. - The presence of a specific term in the potential. - Being complete. Why this is wrong The documentation in physlib/Physlib/Particles/SuperSymmetry/SU5/ChargeSpectrum/Map.lean incorrectly states that "anomaly cancellation" is preserved under the map function, but no lemma in the file supports this assertion. The module defines properties like map_allowsTerm and map_isComplete_iff, which correspond to the documented preservation of potential terms and completeness, respectively. However, ther

📅 Opened Aug 17, 2026💬 0 comments
Quality: 50/100Contribute

⚠️ Found by a local LLM, not a human. This was flagged by an automated documentation-mistake finder (qwen3:14b) and passed 10/10 independent verification runs before filing, but it has not been reviewed by a person. Please check it's a genuine error before acting on it. Summary The documentation in Physlib/Relativity/Tensors/RealTensor/Basic.lean (around line 67) is incorrect. Current text /-- The tensor structure for complex Lorentz tensors. -/ Why this is wrong The docstring for realLorentzTensor incorrectly claims it defines "complex Lorentz tensors", but the declaration's name and surrounding context clearly indicate it is for real tensors. The file's comments explicitly mention "Real Lorentz tensors" and the definition uses Lorentz.ContrMod/Lorentz.CoMod, which are real vector spaces. This discrepancy arises because the docstring was not updated when the definition was renamed from a complex variant to a real one. The correction aligns the documentation with the actual purpo

📅 Opened Aug 17, 2026💬 0 comments
Quality: 50/100Contribute
Looking for more Lean beginner tasks?Explore Lean GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for leanprover-community/physlib

When evaluating whether to contribute to leanprover-community/physlib, 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 leanprover-community/physlib acknowledge new external contributions in approximately 6 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 6.5% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to leanprover-community/physlib

01

Is leanprover-community/physlib welcoming to first-time open-source contributors?

leanprover-community/physlib has a recorded first-timer success rate of 0.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~6 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 59.3 C-Rank™ score represent?

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.3 places leanprover-community/physlib in the Welcoming tier.

04

What is the external contributor pull request merge rate for leanprover-community/physlib?

The external pull request merge rate is 6.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in leanprover-community/physlib?

Yes, leanprover-community/physlib currently has 38 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for leanprover-community/physlib 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.