homarr-labs/homarr - Open Source PR Review Scorecard

A modern and easy to use dashboard. 80+ integrations. 20K+ icons built in. Authentication out of the box. No YAML, drag and drop configuration.

C-Rank Grade: A (Welcoming) - 65/100

External PR Merge Rate: 63%

Response Time: 2d

First Timer Success: 57%

Frequently Asked Questions

Is homarr-labs/homarr welcoming to first-time open-source contributors?

homarr-labs/homarr has a recorded first-timer success rate of 57.1%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in homarr-labs/homarr respond to incoming external pull requests in approximately 56.1 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 65.0 C-Rank™ score (A Tier) represent?

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.0 places homarr-labs/homarr in the A tier.

What is the external contributor pull request merge rate for homarr-labs/homarr?

The external contributor pull request merge rate for homarr-labs/homarr is 62.8%, based on public PR activity from non-core contributors.

Are there Good First Issues available in homarr-labs/homarr?

homarr-labs/homarr currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

homarr-labs
homarr-labs/homarrA•Welcoming5.1k
GitHub
Back to Explorer
homarr-labs

homarr-labs/homarr

5,061
Active (30d)A•Welcoming(65/100)TypeScript

A modern and easy to use dashboard. 80+ integrations. 20K+ icons built in. Authentication out of the box. No YAML, drag and drop configuration.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Strict Quality Architect

Warmth Score
6.8/10
Patience Score
7.3/10
Nitpick Rate
41%

Rigorous architecture standards (62% critical review signals). Ensure PRs strictly follow guidelines before requesting review in homarr-labs/homarr.

Top PR Submission Do's

  • •Add unit tests with >80% coverage for modified code paths
  • •Run repository linter and code formatters locally before pushing
  • •Link relevant GitHub issue ID in PR description pre-flight checklist

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without referencing an existing issue
  • •Do not mix refactoring and feature logic into a single commit
  • •Do not ping maintainers repeatedly within 24 hours of opening
Response Velocity
2 days+
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
62.8%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
57.1%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
49 core
Highly collaborative maintainer core
Diagnostic Health HUD
62.8%
Merge Gauge
57.1%
1st-Timer
Community Vibe42/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for homarr-labs/homarr
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/homarr-labs/homarr)](https://getmerged.abhishekco.de/homarr-labs/homarr?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

Summary The llamacpp integration's getStatsAsync calls /metrics and /slots without a model parameter. On llama.cpp servers running in router mode (multi-model — e.g. llama-server router, llama-swap, and similar front-ends), both endpoints require ?model=<name> and return HTTP 400 model name is missing otherwise. The widget then renders health + model info only; speed/token/slot sections stay empty. Current behavior LlamacppIntegration.getStatsAsync (packages/integrations/src/llama-cpp/llamacpp-integration.ts) fetches bare /health, /v1/models, /metrics, /slots. Against a router-mode server: GET /metrics → 400 {"error":{"message":"model name is missing","type":"api_error"}} GET /slots → 400 (same) GET /metrics?model=gemma-4-26b → 200 (Prometheus text) GET /slots?model=gemma-4-26b → 200 (JSON slot array) /v1/models works fine and returns the model roster — so the integration already has the model name available (models.data[0].id, which is also the model the widget disp

📅 Opened Oct 10, 2026💬 2 comments
Quality: 90/100Contribute

Describe the bug Maybe you're already aware of it but the border color for containers seem not to be applied since the v2 releases. Steps to reproduce Go into edit mode Add a container Edit the container and set a border color for it Save all changes See border color not being applied for this container Impact I'm not aware of any workaround and the severity is of course low, just for the layout. Additional information Version: 2.4.1 (Official build) Browsers: Helium, Zen Exact build or image No response Last working version No response Version Other (describe in "additional information") Installation method Docker Compose Browser Other (describe in "additional information")

📅 Opened Oct 10, 2026💬 4 comments
Quality: 90/100Contribute

Describe the feature you'd like to request Currently, editing and customizing the dashboard layout on mobile devices via touch interaction is frustrating and unreliable. Gestures for dragging, dropping, resizing widgets, or opening specific item settings often fail to respond properly, trigger unwanted page scrolling, or misalign elements. Improved touch support and touch-friendly controls when editing the dashboard on mobile screens: Optimized Touch Drag-and-Drop: Better gesture handling for moving and resizing widgets/icons on touchscreens without triggering native browser scrolling. Larger Touch Targets: Bigger hitboxes or dedicated touch handles for edit buttons, context menus, and drag anchors on small screens. Dedicated Mobile Editing Mode: A touch-optimized editing interface Additional information No response

📅 Opened Oct 3, 2026💬 0 comments
Quality: 50/100Contribute

Describe the feature you'd like to request If I am in transparency mode and want to move an object for example, the calendar and don't know exactly where it is, it is difficult to find; see the video. Bildschirmaufzeichnung.vom.2026-10-03.22-58-48.mp4 Additional information No response

📅 Opened Oct 3, 2026💬 2 comments
Quality: 50/100Contribute

Describe the bug Desktop.2026.05.17.-.19.31.55.01.1.mp4 The admin menu seems to break when you click too many options too fast. Only F5 or ctrl shift r fixes the issue. I tested this wit the latest 1.61.0 stable release and beta-1 Expression  6 Loading the script '<URL>' violates the following Content Security Policy directive: "script-src-elem 'none'". The policy is report-only, so the violation has been logged but no further action has been taken. 0hf6n8w6wz09x.js:13 Uncaught TypeError: Cannot read properties of undefined (reading 'onShowLinkUnderline') at new iZ (0hf6n8w6wz09x.js:13:21354) at sz.createInstance (0hf6n8w6wz09x.js:15:17077) at rY._createRenderer (0hf6n8w6wz09x.js:17:24888) at Object.dispose (0hf6n8w6wz09x.js:1:93084) at h.dispose (0hf6n8w6wz09x.js:1:75958) at rJ._wrappedAddonDispose (0hf6n8w6wz09x.js:17:38413) at i.dispose (0hf6n8w6wz09x.js:17:38144) at rJ.dispose (0hf6n8w6wz09x.js:17:38028) at

📅 Opened May 17, 2026💬 7 comments
Quality: 30/100Contribute
Looking for more TypeScript beginner tasks?Explore TypeScript GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for homarr-labs/homarr

When evaluating whether to contribute to homarr-labs/homarr, 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 homarr-labs/homarr acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 62.8% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to homarr-labs/homarr

01

Is homarr-labs/homarr welcoming to first-time open-source contributors?

homarr-labs/homarr has a recorded first-timer success rate of 57.1%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~2 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 65.0 C-Rank™ score represent?

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.0 places homarr-labs/homarr in the Welcoming tier.

04

What is the external contributor pull request merge rate for homarr-labs/homarr?

The external pull request merge rate is 62.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in homarr-labs/homarr?

Yes, homarr-labs/homarr currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for homarr-labs/homarr 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.