A native macOS browser with Glance for quick lookups and optional local AI.
C-Rank Grade: B (Solid) - 60/100
External PR Merge Rate: 100%
Response Time: <1h
First Timer Success: 100%
nuance-dev/Web 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 nuance-dev/Web respond to incoming external pull requests in approximately 0.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 60.2 places nuance-dev/Web in the B tier.
The external contributor pull request merge rate for nuance-dev/Web is 100.0%, based on public PR activity from non-core contributors.
nuance-dev/Web currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in nuance-dev/Web. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in nuance-dev/Web 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/nuance-dev/Web?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 22:00 UTC (22:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 19:00 to 23:00 UTC (19:00 - 23:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~4 hours (45% approval). Keep your diff compact for rapid review.
Custom API has request-policy tests and six real loopback HTTP tests for redirects, Unicode, response limits and socket cleanup. Those fixtures emulate a server. We still need a full session against an actual Ollama model to check its response/error formats and repeated requests. Start in Web/AI/Services/CompatibleAPIProvider.swift, Web/AI/Services/CompatibleAPIConfiguration.swift, WebTests/CompatibleAPITransportTests.swift, and the custom API cases in WebTests/AIProviderTests.swift. Ollama documents its OpenAI-compatible endpoint here. Run a local Ollama server with a model already installed. In Web's AI settings, enter http://localhost:11434/v1, that exact model ID, and the loopback-only option to omit an API key. Select Custom API and ask a short question. Confirm streamed text arrives, Stop ends the request, and a second request works. Open a public article. Check page text is absent before consent, included after consent, and always excluded for a private tab. Use a local request
Glance defaults to Control-Option-Space. With Control-Option as the VoiceOver modifier, that is also VoiceOver's command to activate the focused control. Apple documents the command here. The shortcut collision is confirmed from source; its runtime effect still needs a VoiceOver check. Start in Web/Services/PeekController.swift: shortcut, registerShortcut(), and the local key monitor in start(). The local monitor consumes the matching event even when global registration fails. Settings live in Web/Views/Components/PeekView.swift (PeekSettingsView). Enable VoiceOver with the Control-Option modifier and leave Glance on its default shortcut. Focus a button in Web and press Control-Option-Space. Repeat in another app and in Glance itself. Toggle VoiceOver while Web is running and repeat. The selected control should activate normally. If Glance intercepts it, suspend that shortcut while VoiceOver is enabled and offer a different binding or a disabled global shortcut. Cover both Carbon reg
Glance's geometry tests cover a secondary display with a negative origin and a small display. They do not exercise real display changes. We need a check on a Mac with two displays before claiming this behavior is verified. Start in Web/Services/PeekController.swift: show() chooses the display under the pointer, reposition(animated:) uses visibleFrame, and the screen-change observer calls it again. reposition currently identifies the selected screen by object identity. Existing arithmetic checks are in WebTests/PeekGeometryTests.swift. Put the second display to the left of the main display. Open Glance on each and expand a public page. Move the Dock between the bottom and a side. Check that the input and expanded card fit the usable display area. Keep Glance pinned on the second display, change its scaling, then disconnect it. Glance should keep the same visible corner while expanding. A display that remains connected should keep its card after a settings change; disconnecting it shou
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 nuance-dev/Web, 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 nuance-dev/Web acknowledge new external contributions in approximately <1 hour. 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.
nuance-dev/Web 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 ~<1 hour. 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 60.2 places nuance-dev/Web 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, nuance-dev/Web currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for nuance-dev/Web 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.