The self-hosted Linktree alternative. Import from any competitor in 30 seconds. Multi-page, privacy-respecting analytics, one-line install.
C-Rank Grade: B (Solid) - 54/100
External PR Merge Rate: 67%
Response Time: 18h
First Timer Success: 100%
Manak-hash/LinkBreeze 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 Manak-hash/LinkBreeze respond to incoming external pull requests in approximately 17.9 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 53.7 places Manak-hash/LinkBreeze in the B tier.
The external contributor pull request merge rate for Manak-hash/LinkBreeze is 66.7%, based on public PR activity from non-core contributors.
Manak-hash/LinkBreeze currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
The self-hosted Linktree alternative. Import from any competitor in 30 seconds. Multi-page, privacy-respecting analytics, one-line install.
Collaborative maintainer environment in Manak-hash/LinkBreeze. Reviews community pull requests with focus on project quality.
Discussions in Manak-hash/LinkBreeze 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/Manak-hash/LinkBreeze?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 02:00 UTC (02:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~12 hours (83% approval). Large PRs (>500 lines) take ~86 hours (30% approval). Keep your diff compact for rapid review.
Problem There's no programmatic way to manage links, profile, or settings. Every link-in-bio competitor (Linktree, LinkStack) has an API. Without one, LinkBreeze can't integrate with CI pipelines, scripts, or third-party tools. Proposed design Authentication: API key stored in settings table (generated in admin panel). Sent via Authorization: Bearer <key> header. Endpoints: GET /api/v1/links List all links POST /api/v1/links Create a link PUT /api/v1/links/:id Update a link DELETE /api/v1/links/:id Delete a link PUT /api/v1/links/reorder Reorder links (array of IDs) GET /api/v1/profile Get profile PUT /api/v1/profile Update profile GET /api/v1/analytics Get analytics (views, clicks, top links) Prep work already done The queries layer (src/server/queries/) already abstracts all DB access The metadata JSON column on links was added for future extensibility ADR-0004 documents the data abstraction Scope This is a larg
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 Manak-hash/LinkBreeze, 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 Manak-hash/LinkBreeze acknowledge new external contributions in approximately 17 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 66.7% were successfully merged into the primary branch.
Manak-hash/LinkBreeze 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 ~17 hours. 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 53.7 places Manak-hash/LinkBreeze in the Solid tier.
The external pull request merge rate is 66.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Manak-hash/LinkBreeze 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 Manak-hash/LinkBreeze 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.