xssnick/tonutils-go - Open Source PR Review Scorecard

TON SDK Library in pure Golang for interacting with The Open Network ecosystem using native protocols, such as ADNL, RLDP and etc.

C-Rank Grade: C (Moderate) - 39/100

External PR Merge Rate: 60%

Response Time: 22d

First Timer Success: -

Frequently Asked Questions

Is xssnick/tonutils-go welcoming to first-time open-source contributors?

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

What does the 38.7 C-Rank™ score (C 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 38.7 places xssnick/tonutils-go in the C tier.

What is the external contributor pull request merge rate for xssnick/tonutils-go?

The external contributor pull request merge rate for xssnick/tonutils-go is 60.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in xssnick/tonutils-go?

xssnick/tonutils-go does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

xssnick
xssnick/tonutils-goC•Moderate685
GitHub
Back to Explorer
xssnick

xssnick/tonutils-go

685
InactiveC•Moderate(39/100)Low Sample (<20 PRs)Go

TON SDK Library in pure Golang for interacting with The Open Network ecosystem using native protocols, such as ADNL, RLDP and etc.

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 xssnick/tonutils-go 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
22 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
60.0%
Moderate 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
1 core
Single maintainer review bottleneck
Diagnostic Health HUD
60.0%
Merge Gauge
0.0%
1st-Timer
Community Vibe24/100

Embed C-Rank Badge

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

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

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for xssnick/tonutils-go.

View all good first issues directly on GitHub

Looking for more Go beginner tasks?Explore Go 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 xssnick/tonutils-go

When evaluating whether to contribute to xssnick/tonutils-go, 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 xssnick/tonutils-go acknowledge new external contributions in approximately 22 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 60.0% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to xssnick/tonutils-go

01

Is xssnick/tonutils-go welcoming to first-time open-source contributors?

xssnick/tonutils-go has a recorded first-timer success rate of 0.0%. Repositories ranked Moderate 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 ~22 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 38.7 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 38.7 places xssnick/tonutils-go in the Moderate tier.

04

What is the external contributor pull request merge rate for xssnick/tonutils-go?

The external pull request merge rate is 60.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 xssnick/tonutils-go?

xssnick/tonutils-go 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 xssnick/tonutils-go 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.