Fast indexing and search of discontinuous motifs in protein structures
C-Rank Grade: D (Risky) - 20/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
steineggerlab/folddisco 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.
Maintainers in steineggerlab/folddisco 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 19.5 places steineggerlab/folddisco in the D tier.
The external contributor pull request merge rate for steineggerlab/folddisco is 0.0%, based on public PR activity from non-core contributors.
steineggerlab/folddisco currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in steineggerlab/folddisco. Reviews community pull requests with focus on project quality.
Discussions in steineggerlab/folddisco focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/steineggerlab/folddisco?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 05:00 to 09:00 UTC (05:00 - 09:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
Hi, In some of my outputs, query_residues has one more entry than matching_residues. I ran the command below: folddisco query -i index/mouse -q query/mouse_motifs.txt -t 20 --tm-score 0.25 --rmsd 3.5 --header --format-output qid,tid,node_count,tm_score,idf,rmsd,matching_residues,query_residues Example output: qid tid node_count tm_score idf rmsd matching_residues query_residues query.pdb target.pdb 11 0.2692 356.7002 3.0368 A196,A215,_,A231,A232,A233,A205,A240,A242,A243,A244,A246,_ A545,A564,A574,A580,A581,A582,A583,A584,A591,A592,A593,A595,A632,A635 Since _ is documented as the placeholder for no match, I expected matching_residues and query_residues to stay aligned and have the same number of comma-separated entries. In this example, matching_residues has 13 entries and query_residues has 14 entries. Is this expected, or could it be an output inconsistency?
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 steineggerlab/folddisco, 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 steineggerlab/folddisco acknowledge new external contributions in approximately -. 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.
steineggerlab/folddisco 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.
The initial maintainer response time averages ~-. 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 19.5 places steineggerlab/folddisco in the Risky tier.
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.
Yes, steineggerlab/folddisco 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 steineggerlab/folddisco 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.