spoo.me is an open-source & API first link management infra
C-Rank Grade: A (Welcoming) - 61/100
External PR Merge Rate: 78%
Response Time: 5h
First Timer Success: 100%
spoo-me/spoo has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in spoo-me/spoo respond to incoming external pull requests in approximately 5.3 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 61.1 places spoo-me/spoo in the A tier.
The external contributor pull request merge rate for spoo-me/spoo is 77.6%, based on public PR activity from non-core contributors.
spoo-me/spoo currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in spoo-me/spoo welcoming community pull requests and bug fixes.
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/spoo-me/spoo?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 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~25 hours (35% approval). Keep your diff compact for rapid review.
Explanation Design and implement a comprehensive abuse prevention framework for spoo.me to reduce phishing, scam, and spam links while preserving the platform's privacy-first philosophy and keeping false positives as low as possible. Is your feature request related to a problem? Please describe. As spoo.me has grown, it has increasingly become a target for abuse by scammers and phishing campaigns. Recently, this has resulted in reputation issues, including warnings from external security providers, which negatively affect legitimate users and the platform as a whole. While individual malicious links can be blocked manually, this approach does not scale. We need a long-term system that can proactively detect, prevent, and respond to abuse while minimizing the impact on legitimate users. Describe the solution you'd like Create a modular abuse prevention framework that can evolve over time. Some ideas include (but are not limited to): Risk scoring for newly created links. Domain and dest
Concerning discussion #93 https://github.com/orgs/spoo-me/discussions/93 about if it's possible to limit password attempts or something along those lines as a security measure. btw Cloudflare still complains about phising.
Explanation Please add an optional “reuse existing shortlink” mode for the API (authenticated accounts only). When enabled, submitting the same long URL should always return the same shortlink instead of generating a new one each time. Is your feature request related to a problem? Please describe. Right now, sending the same long URL to the API multiple times creates multiple different shortlinks. This leads to duplicates, makes link management difficult, and can split tracking/analytics across many short URLs for the same destination. Describe the solution you'd like Add an account-level toggle (or an authenticated-only API option) like: “Return existing shortlink for identical long URL”. If enabled and the long URL already exists within the same account, the API should return the existing shortlink. If it doesn’t exist yet, it should create it once and then reuse it for future requests. This behavior should not apply to unauthenticated/free usage. Describe alternatives yo
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 spoo-me/spoo, 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 spoo-me/spoo acknowledge new external contributions in approximately 5 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 77.6% were successfully merged into the primary branch.
spoo-me/spoo has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~5 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 61.1 places spoo-me/spoo in the Welcoming tier.
The external pull request merge rate is 77.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, spoo-me/spoo currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for spoo-me/spoo 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.