aiming-lab/AutoResearchClaw - Open Source PR Review Scorecard

Fully autonomous & self-evolving research from idea to paper. Chat an Idea. Get a Paper. 🦞

C-Rank Grade: B (Solid) - 41/100

External PR Merge Rate: 20%

Response Time: <1h

First Timer Success: -

Frequently Asked Questions

Is aiming-lab/AutoResearchClaw welcoming to first-time open-source contributors?

aiming-lab/AutoResearchClaw has a recorded first-timer success rate of 0.0%. Repositories ranked B 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 aiming-lab/AutoResearchClaw respond to incoming external pull requests in approximately 0.8 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 41.4 C-Rank™ score (B 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 41.4 places aiming-lab/AutoResearchClaw in the B tier.

What is the external contributor pull request merge rate for aiming-lab/AutoResearchClaw?

The external contributor pull request merge rate for aiming-lab/AutoResearchClaw is 20.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in aiming-lab/AutoResearchClaw?

aiming-lab/AutoResearchClaw does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

aiming-lab
aiming-lab/AutoResearchClawBSolid14.0k
GitHub
Back to Explorer
aiming-lab

aiming-lab/AutoResearchClaw

14,043
BSolid(41/100)Python

Fully autonomous & self-evolving research from idea to paper. Chat an Idea. Get a Paper. 🦞

Compare
Jump to:
Response Velocity
<1 hour
⚡ Fast reviewer response

Average Response Latency

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

Merge Efficiency
20.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
20.0%
Merge Gauge
0.0%
1st-Timer
Community Vibe37/100

Embed C-Rank Badge

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

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

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for aiming-lab/AutoResearchClaw.

View all good first issues directly on GitHub

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 aiming-lab/AutoResearchClaw

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

Frequently Asked Questions - Contributing to aiming-lab/AutoResearchClaw

01

Is aiming-lab/AutoResearchClaw welcoming to first-time open-source contributors?

aiming-lab/AutoResearchClaw has a recorded first-timer success rate of 0.0%. Repositories ranked Solid 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 41.4 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 41.4 places aiming-lab/AutoResearchClaw in the Solid tier.

04

What is the external contributor pull request merge rate for aiming-lab/AutoResearchClaw?

The external pull request merge rate is 20.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 aiming-lab/AutoResearchClaw?

aiming-lab/AutoResearchClaw does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for aiming-lab/AutoResearchClaw 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.