davidpagnon/Sports2D - Open Source PR Review Scorecard

Compute 2D human pose and angles from a video or a webcam.

C-Rank Grade: D (Risky) - 27/100

External PR Merge Rate: -

Response Time: <1h

First Timer Success: -

Frequently Asked Questions

Is davidpagnon/Sports2D welcoming to first-time open-source contributors?

davidpagnon/Sports2D has a recorded first-timer success rate of 0.0%. Repositories ranked D 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 davidpagnon/Sports2D 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.

What does the 26.9 C-Rank™ score (D 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 26.9 places davidpagnon/Sports2D in the D tier.

What is the external contributor pull request merge rate for davidpagnon/Sports2D?

The external contributor pull request merge rate for davidpagnon/Sports2D is 0.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in davidpagnon/Sports2D?

davidpagnon/Sports2D currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

davidpagnon
davidpagnon/Sports2DD•Risky287
GitHub
Back to Explorer
davidpagnon

davidpagnon/Sports2D

287
InactiveD•Risky(27/100)Low Sample (<20 PRs)Python

Compute 2D human pose and angles from a video or a webcam.

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 davidpagnon/Sports2D 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
<1 hour
⚡ Fast reviewer response

Average Response Latency

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

Merge Efficiency
0.0%
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
2 core
Small core review team
Diagnostic Health HUD
0.0%
Merge Gauge
0.0%
1st-Timer
Community Vibe30/100

Embed C-Rank Badge

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

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

Active Good First Issues (1)

View on GitHub

Your OS Windows Your Python version Python 3.11 What is your library version? Pose2sim v0.10.49; sports2d 0.8.32 Your problem Hey there, I know this has already been addressed in #35, but wanted to share our case in case it's useful for narrowing down the cause. We're part of a research team doing postural analysis of running on a treadmill. We're seeing joint angles switch back and forth mid-run. mode: performance reduces it noticeably, but it's quite bad on balanced. A couple of things on our end: Video is captured in sagittal view, as parallel to the motion plane as possible, per the docs. Camera: Panasonic HV-V7700, 1080p @ 50fps. Questions: Is this switching mode-dependent or is there something else going on? Would you expect framerate to meaningfully help here, or is this purely a pose-model-accuracy issue? Params: { "time_range": "", "nb_persons_to_detect": "all", "person_ordering_method": "first_detected", "first_person_height": "1.65", "pose_model": "body_with_feet", "mode":

📅 Opened Jul 28, 2026💬 3 comments
Quality: 90/100Contribute
Looking for more Python beginner tasks?Explore Python 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 davidpagnon/Sports2D

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

Frequently Asked Questions - Contributing to davidpagnon/Sports2D

01

Is davidpagnon/Sports2D welcoming to first-time open-source contributors?

davidpagnon/Sports2D has a recorded first-timer success rate of 0.0%. Repositories ranked Risky 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 ~<1 hour. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 26.9 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 26.9 places davidpagnon/Sports2D in the Risky tier.

04

What is the external contributor pull request merge rate for davidpagnon/Sports2D?

The external pull request merge rate is 0.0%. 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 davidpagnon/Sports2D?

Yes, davidpagnon/Sports2D currently has 1 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 davidpagnon/Sports2D 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.