rorkai/App-Store-Connect-CLI - Open Source PR Review Scorecard

Fast, scriptable CLI for the App Store Connect API. Automate TestFlight, builds, submissions, signing, analytics, screenshots, subscriptions, and more

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

External PR Merge Rate: 78%

Response Time: -

First Timer Success: 88%

Frequently Asked Questions

Is rorkai/App-Store-Connect-CLI welcoming to first-time open-source contributors?

rorkai/App-Store-Connect-CLI has a recorded first-timer success rate of 87.5%. 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 rorkai/App-Store-Connect-CLI 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 60.2 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 60.2 places rorkai/App-Store-Connect-CLI in the A tier.

What is the external contributor pull request merge rate for rorkai/App-Store-Connect-CLI?

The external contributor pull request merge rate for rorkai/App-Store-Connect-CLI is 77.7%, based on public PR activity from non-core contributors.

Are there Good First Issues available in rorkai/App-Store-Connect-CLI?

rorkai/App-Store-Connect-CLI does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

rorkai
rorkai/App-Store-Connect-CLIA•Welcoming7.5k
GitHub
Back to Explorer
rorkai

rorkai/App-Store-Connect-CLI

7,526
Active (30d)A•Welcoming(60/100)Go

Fast, scriptable CLI for the App Store Connect API. Automate TestFlight, builds, submissions, signing, analytics, screenshots, subscriptions, and more

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Constructive Code Reviewer

Warmth Score
7.7/10
Patience Score
8.0/10
Nitpick Rate
29%

Balanced & professional review environment in rorkai/App-Store-Connect-CLI. Maintains strict focus on technical quality and test standards.

Top PR Submission Do's

  • •Add unit tests with >80% coverage for modified code paths
  • •Run repository linter and code formatters locally before pushing
  • •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
-
No reviewer activity recorded

Average Response Latency

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

Merge Efficiency
77.7%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
87.5%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
3 core
Small core review team
Diagnostic Health HUD
77.7%
Merge Gauge
87.5%
1st-Timer
Community Vibe57/100

Embed C-Rank Badge

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

GetMerged C-Rank badge for rorkai/App-Store-Connect-CLI
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/rorkai/App-Store-Connect-CLI)](https://getmerged.abhishekco.de/rorkai/App-Store-Connect-CLI?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

Summary Add --max-devices N to asc devices register --via-url so one shared registration URL or QR code can't register an unbounded number of devices, and verify the full flow on a real iPhone. Motivation #2770 made each callback token single-use and bound to one device, but kept the registration URL reusable for the whole session so one QR code can collect several testers. Anyone who obtains the URL during --ttl can therefore register additional devices against the team's device quota (100 per device family per membership year). A cap is the natural bound, and the flow has never been exercised on real hardware. Current behavior (verified on origin/main 3f1a758) internal/cli/devices/devices_via_url.go: each downloaded profile carries a random 128-bit callback token; unused tokens are capped at 1024 per session (profile downloads past that get 503). --ttl bounds the session (waitCtx via context.WithTimeout). There is no limit on registered devices per session. --stream prints one JSON

📅 Opened Sep 27, 2026💬 0 comments
Quality: 80/100Contribute

Summary 47 of 170 installs hit 409 on asc pricing schedule create (5.x, 14 days), and #2606 showed the rate is independent of --start-date. POST /v1/appPriceSchedules is the only write verb (no PATCH/DELETE) and replaces the app's single schedule, so it is not an existence conflict and --if-exists does not map. What to do Capture Apple's real 409 body for this endpoint (the disposable app 6759231657 is authorized for live mutations of this kind if needed; record what was run), then map the code/detail to a specific, actionable error message (e.g. a schedule change already pending, base territory mismatch, price point not available in a territory) and classify it correctly for telemetry. Acceptance criteria the real 409 body checked in as a fixture specific message per identified cause; other 409s unchanged

📅 Opened Sep 15, 2026💬 0 comments
Quality: 80/100Contribute

Summary --profile selects the API-key profile but is only bound on some commands. Telemetry (5.x, 14 days): 86 distinct installs passed --profile to 75 commands that do not define it (apps list 31, auth status 18, …) and got unknown-flag errors. Proposed fix Bind --profile at the root FlagSet (as --output/--api-debug are) so it is accepted before or after the subcommand on every command, with the same semantics as today's per-command flag; remove the per-command duplicates if they become redundant. Note the @env:/@file: indirection PR (#2585) excludes root-owned --profile; keep that exclusion. Acceptance criteria asc apps list --profile X and asc --profile X apps list both resolve the profile existing per-command --profile behavior unchanged; help regenerated

📅 Opened Sep 15, 2026💬 0 comments
Quality: 80/100Contribute

Summary asc screenshots list missing_required on --locale: 92 distinct installs (5.x, 14 days). Agents frequently do not know the locale set before listing. Proposed fix Either default --locale to the version's primary locale (printing the choice on stderr), or, when omitted, list screenshots across all localizations of the selected version with a locale column/field. Prefer the second if the output shape can stay additive; otherwise the first. In the error path, list the locales that exist for the version. Acceptance criteria cmdtest for omitted --locale behavior and for the enumerated error when the version has no localizations JSON contract remains additive

📅 Opened Sep 15, 2026💬 0 comments
Quality: 80/100Contribute

Summary asc pricing schedule create is the top missing_required hotspot after the ones already fixed: 99 distinct installs (5.x, 14 days) omitted --start-date, and 46 hit 409 conflicts afterwards. Proposed fix Default --start-date to today's date (UTC, the format Apple expects) when omitted; print the chosen date on stderr. Keep explicit values authoritative; reject malformed dates with exit 2 and the expected format. Note in help that Apple requires the date to be today or later. Acceptance criteria cmdtest: omitted flag sends today's date and prints the note; explicit flag unchanged; malformed → exit 2 help/docs updated

📅 Opened Sep 15, 2026💬 0 comments
Quality: 80/100Contribute
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 rorkai/App-Store-Connect-CLI

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

Frequently Asked Questions - Contributing to rorkai/App-Store-Connect-CLI

01

Is rorkai/App-Store-Connect-CLI welcoming to first-time open-source contributors?

rorkai/App-Store-Connect-CLI has a recorded first-timer success rate of 87.5%. 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 ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 60.2 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 60.2 places rorkai/App-Store-Connect-CLI in the Welcoming tier.

04

What is the external contributor pull request merge rate for rorkai/App-Store-Connect-CLI?

The external pull request merge rate is 77.7%. 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 rorkai/App-Store-Connect-CLI?

rorkai/App-Store-Connect-CLI 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 rorkai/App-Store-Connect-CLI 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.