A development and test oriented OAuth2 mock server
C-Rank Grade: B (Solid) - 51/100
External PR Merge Rate: 100%
Response Time: 11d
First Timer Success: 100%
axa-group/oauth2-mock-server has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in axa-group/oauth2-mock-server respond to incoming external pull requests in approximately 275.8 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 51.2 places axa-group/oauth2-mock-server in the B tier.
The external contributor pull request merge rate for axa-group/oauth2-mock-server is 100.0%, based on public PR activity from non-core contributors.
axa-group/oauth2-mock-server currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
A development and test oriented OAuth2 mock server
Collaborative maintainer environment in axa-group/oauth2-mock-server. Reviews community pull requests with focus on project quality.
Discussions in axa-group/oauth2-mock-server focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/axa-group/oauth2-mock-server?utm_source=github&utm_medium=badge)
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 Tuesday - Thursday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~179 hours (96% approval). Large PRs (>500 lines) take ~1324 hours (45% approval). Keep your diff compact for rapid review.
Summary I'd like to be able to customise the resulting JSON given by /.well-known/openid-configuration. Desired solution Something slimilar to the existing Events server.service.once(Events.BeforeWellKnownDocument, callback) As long as the callback as access to the document, and is able to either replace it or mutate it, I'm happy. Alternative solutions I've tried adding a route with /.well-known/openid-configuration while configuring the server to have a different wellKnownDocument endpoint. Additional Context My usecase is running oauth2-mock-server in a container with oauth2-proxy so we have automatic redirect to the url defined by authorization_endpoint as defined in /.well-known/openid-configuration. In this case, I'd like that to be a link to localhost rather than the issuer URL.
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 axa-group/oauth2-mock-server, 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 axa-group/oauth2-mock-server acknowledge new external contributions in approximately 11 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
axa-group/oauth2-mock-server has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~11 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 51.2 places axa-group/oauth2-mock-server in the Solid tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, axa-group/oauth2-mock-server 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 axa-group/oauth2-mock-server 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.