The authentication glue you need.
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 75%
Response Time: 4d
First Timer Success: 50%
goauthentik/authentik 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.
Maintainers in goauthentik/authentik respond to incoming external pull requests in approximately 85.3 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 59.2 places goauthentik/authentik in the A tier.
The external contributor pull request merge rate for goauthentik/authentik is 74.8%, based on public PR activity from non-core contributors.
goauthentik/authentik 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 goauthentik/authentik. 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/goauthentik/authentik?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 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~55 hours (93% approval). Large PRs (>500 lines) take ~410 hours (34% approval). Keep your diff compact for rapid review.
Is your feature request related to a problem? The policies table (Customization -> Policies) has 3 columns: Name (sortable), Type (unsortable), and Actions. I'd like to have a "last edited" column so I can easily sort and see the policies I am working on or that somebody recently changed on top. Otherwise I have to hunt for them by name. This applies to many other tables: Property Mappings, Files, Flows, Stages, Providers, Apps, etc. I know this should be possible because some tables already have this column. Reputation Scores have a sortable "Updated" column and Blueprints have "Last applied" column. Describe the solution you'd like No response Describe alternatives that you've considered I tried not having the column and it was not very convenient. Additional context 2026.5.4
Describe the bug Bug: Runtime values are used as structured log event names or field keys Anti-pattern This report identifies logging calls where dynamic runtime data is used as the log event name or as a structured field key. In structured logging, event names and field keys should be stable schema elements. Runtime-specific data such as IDs, URLs, object names, errors, query labels, or caller-controlled keys should be emitted as field values under stable keys instead of changing the event or key surface. Impact on observability platforms When event names or field keys vary with runtime data, observability backends can see unnecessary cardinality growth in log streams, indexes, facets, labels, and dashboards. This makes queries harder to write, splits one logical event across many names or fields, increases storage and indexing cost, and can reduce the usefulness of alerts and aggregations. When opaque identifiers or shifted key/value pairs become field names, the resulting records ar
An option/flag to automatically set reputation score back to 0 for a user/IP upon successful login. Rather than just increasing reputation score by one.
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 goauthentik/authentik, 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 goauthentik/authentik acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 74.8% were successfully merged into the primary branch.
goauthentik/authentik 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.
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 59.2 places goauthentik/authentik in the Welcoming tier.
The external pull request merge rate is 74.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, goauthentik/authentik 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 goauthentik/authentik 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.