Cutting-edge tools powering Angular full-stack development.
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 82%
Response Time: -
First Timer Success: 76%
spartan-ng/spartan has a recorded first-timer success rate of 76.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in spartan-ng/spartan 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.
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.4 places spartan-ng/spartan in the A tier.
The external contributor pull request merge rate for spartan-ng/spartan is 82.2%, based on public PR activity from non-core contributors.
spartan-ng/spartan currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Cutting-edge tools powering Angular full-stack development.
Highly welcoming maintainers in spartan-ng/spartan. Prompt code reviews with positive guidance for new contributors.
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/spartan-ng/spartan?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 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (37% approval). Keep your diff compact for rapid review.
Scope popover, dialog Information Problem BrnDialog (and therefore BrnPopover) only exposes closeOnOutsidePointerEvents as a boolean. There is no way to conditionally keep the dialog/popover open for a specific outside pointer event. This breaks a very common composition: an overlay-based component opened from inside a popover — e.g. a brn-select (or any CDK-overlay component: autocomplete, combobox, menu, nested popover) placed inside brn-popover's content. brn-select renders its listbox in its own CDK overlay, which is a sibling of the popover's overlay in the global overlay container — not a DOM descendant of the popover's pane. So a pointer interaction with the open select panel (or its backdrop) counts as an outside pointer event for the popover. With closeOnOutsidePointerEvents enabled (the default for brn-popover), the popover tears itself down together with the select the moment the user clicks the select. Result: you cannot reliably put a select/combobox/menu inside a popo
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 spartan-ng/spartan, 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 spartan-ng/spartan acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 82.2% were successfully merged into the primary branch.
spartan-ng/spartan has a recorded first-timer success rate of 76.5%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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.4 places spartan-ng/spartan in the Welcoming tier.
The external pull request merge rate is 82.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, spartan-ng/spartan 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 spartan-ng/spartan 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.