The official Sentry SDK for iOS, tvOS, macOS, watchOS, iPadOS and visionOS.
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 79%
Response Time: 3d
First Timer Success: 67%
getsentry/sentry-cocoa has a recorded first-timer success rate of 66.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in getsentry/sentry-cocoa respond to incoming external pull requests in approximately 74.7 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 65.4 places getsentry/sentry-cocoa in the A tier.
The external contributor pull request merge rate for getsentry/sentry-cocoa is 78.6%, based on public PR activity from non-core contributors.
getsentry/sentry-cocoa currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in getsentry/sentry-cocoa. Maintains strict focus on technical quality and test standards.
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/getsentry/sentry-cocoa?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 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~49 hours (96% approval). Large PRs (>500 lines) take ~358 hours (35% approval). Keep your diff compact for rapid review.
Remove enableMetrics flag from the SDK
Description SentryObjCInternalProfilingApiIntegrationTests.testCollect_shouldContainTransactionInfo fails intermittently because profile collection returns nil. Observed failure: CI job: https://github.com/getsentry/sentry-cocoa/actions/runs/30562889192/job/90940194442?pr=8600 payload[@"transaction"] was nil The rerun of the same iOS 26 Bitrise job passed Investigation SentryProfileCollector adds the transaction dictionary unconditionally whenever profile serialization returns a payload. Therefore, the missing transaction means the entire payload was nil, rather than transaction metadata being omitted. Profile serialization returns nil when either: fewer than two samples were collected, or fewer than two samples fall inside the requested interval The test sleeps for 200 ms and then always requests the fixed interval [startTime, startTime + 200 ms]. The profiler samples asynchronously at 101 Hz. Under CI load, a delayed sampling thread can produce too few samples before the fixed cu
Motivation We refer to the apps in Samples/ as "sample apps", but we mostly use them for development and CI UI tests — not as reference samples for users. The "sample" label misleads users into treating them as learning material, when the code is written for testing and is hard to follow as an example. We should do a full rename of "sample apps" → "test apps" across the repo (directories, targets, Makefile, CI, and docs).
Add a boolean enableBreadcrumbTextExtraction (default true) on SentryOptions. When false, skip child text extraction — only sentryLabel, accessibilityIdentifier, and UIButton.currentTitle are captured.
Add a set of view class names to filter from interaction breadcrumbs. Check in SentryBreadcrumbTracker.extractData() and SentryUIEventTracker. Pattern already exists in replay's SentryRedactOptions.excludedViewClasses.
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 getsentry/sentry-cocoa, 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 getsentry/sentry-cocoa acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 78.6% were successfully merged into the primary branch.
getsentry/sentry-cocoa has a recorded first-timer success rate of 66.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 days+. 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 65.4 places getsentry/sentry-cocoa in the Welcoming tier.
The external pull request merge rate is 78.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, getsentry/sentry-cocoa 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 getsentry/sentry-cocoa 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.