TimMcCool/scratchattach - Open Source PR Review Scorecard

Scratch API wrapper with support for almost all site features, cloud requests framework and more

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

External PR Merge Rate: 78%

Response Time: 17h

First Timer Success: 50%

Frequently Asked Questions

Is TimMcCool/scratchattach welcoming to first-time open-source contributors?

TimMcCool/scratchattach has a recorded first-timer success rate of 50.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 TimMcCool/scratchattach respond to incoming external pull requests in approximately 17.1 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 55.6 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 55.6 places TimMcCool/scratchattach in the A tier.

What is the external contributor pull request merge rate for TimMcCool/scratchattach?

The external contributor pull request merge rate for TimMcCool/scratchattach is 78.2%, based on public PR activity from non-core contributors.

Are there Good First Issues available in TimMcCool/scratchattach?

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

TimMcCool
TimMcCool/scratchattachA•Welcoming247
GitHub
Back to Explorer
TimMcCool

TimMcCool/scratchattach

247
InactiveA•Welcoming(56/100)Python

Scratch API wrapper with support for almost all site features, cloud requests framework and more

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

High-Friction Gatekeeper

Warmth Score
5.0/10
Patience Score
6.0/10
Nitpick Rate
65%

Rigorous architecture standards (100% critical review signals). Ensure PRs strictly follow guidelines before requesting review in TimMcCool/scratchattach.

Top PR Submission Do's

  • •Add unit tests with >80% coverage for modified code paths
  • •Use conventional commit messages and clean branch names
  • •Link relevant GitHub issue ID in PR description pre-flight checklist

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without referencing an existing issue
  • •Do not mix refactoring and feature logic into a single commit
  • •Do not ping maintainers repeatedly within 24 hours of opening
Response Velocity
17 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
78.2%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
50.0%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
1 core
Single maintainer review bottleneck
Diagnostic Health HUD
78.2%
Merge Gauge
50.0%
1st-Timer
Community Vibe63/100

Embed C-Rank Badge

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

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

Active Good First Issues (2)

View on GitHub

add a feature to set profile picture you will need to use requests no error handling prototype: requests.post(f"https://scratch.mit.edu/site-api/users/all/{sess.username}/", headers=sess._headers, cookies=sess._cookies, files={"image": pfp_path.read_bytes()})

📅 Opened May 16, 2026💬 0 comments
Quality: 55/100Contribute

scratchattach version 2.1.18 What happened? I tried making a project, setting desc, and sharing it. It errored in the share part. I am using termux Your code. import scratchattach as sa def main(): sess = sa.login("faretek", "redacted") proj = sess.create_project(title="test btw") proj.set_instructions("i made this on my phone ig") proj.share() if __name__ == "__main__": main() Traceback (sat) [u0_a189@localhost sat]$ uv run main.py /data/data/com.termux/files/home/locode/sat/.venv/lib/python3.13/site-packages/scratchattach/site/session.py:1102: LoginDataWarning: IMPORTANT: If you included login credentials directly in your code (e.g. session_id, session_string, ...), then make sure to EITHER instead load them from environment variables or files OR remember to remove them before you share your code with anyone else. If you want to remove this warning, use `warnings.filterwarnings('ignore', category=scratchattach.LoginDataWarning)` warnings.warn( Traceback (most

📅 Opened May 9, 2026💬 1 comment
Quality: 80/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 TimMcCool/scratchattach

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

Frequently Asked Questions - Contributing to TimMcCool/scratchattach

01

Is TimMcCool/scratchattach welcoming to first-time open-source contributors?

TimMcCool/scratchattach has a recorded first-timer success rate of 50.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 ~17 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 55.6 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 55.6 places TimMcCool/scratchattach in the Welcoming tier.

04

What is the external contributor pull request merge rate for TimMcCool/scratchattach?

The external pull request merge rate is 78.2%. 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 TimMcCool/scratchattach?

Yes, TimMcCool/scratchattach currently has 2 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 TimMcCool/scratchattach 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.