Spreading Thankfulness in Open Source.
C-Rank Grade: S (Elite) - 73/100
External PR Merge Rate: 89%
Response Time: 6h
First Timer Success: 60%
BlitzKraft/saythanks.io has a recorded first-timer success rate of 60.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in BlitzKraft/saythanks.io respond to incoming external pull requests in approximately 5.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 73.2 places BlitzKraft/saythanks.io in the S tier.
The external contributor pull request merge rate for BlitzKraft/saythanks.io is 88.9%, based on public PR activity from non-core contributors.
BlitzKraft/saythanks.io currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in BlitzKraft/saythanks.io. Ensure PR scope matches issue requirements closely before requesting review.
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/BlitzKraft/saythanks.io?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 17:00 UTC (17:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~28 hours (40% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Python.
A plugin for live interpretation of video streams
Subagent Delegation framework for Pydantic AI, enabling nested subagents that can spawn their own specialists on-the-fly, with smart sync/async/auto mode selection, runtime agent creation, and clean multi-agent architecture. Adds specialization, parallel execution, and task cancellation.
CredSweeper is a tool to detect credentials in any directories or files. CredSweeper could help users to detect unwanted exposure of credentials (such as token, passwords, api keys etc.) in advance. By scanning lines, filtering, and using AI model as option, CredSweeper reports lines with possible credentials, where the line is, and expected type o
Overview Add a robust email validation mechanism that serves as a gatekeeper for all user profile updates and data persistence operations, irrespective of the authentication provider (Facebook, Google, etc.). Technical Requirements Email Validation Logic Implement a validation function that checks whether the email string retrieved from the OAuth provider is: Not null or None Not an empty string Conforms to a valid email format (RFC 5322 compliant) Contains necessary components (local-part and domain-part separated by '@') Pre-Update Validation Flow Integrate the email validation check into the user authentication pipeline Ensure validation occurs before any database write operations Apply this validation universally across all OAuth providers (Facebook, Google, GitHub, etc.) Return a meaningful error message if validation fails Implementation Scope Modify the authentication handler to invoke email validation immediately after receiving user_detailed_info from the OAuth provide
Describe the bug When authenticating with FaceBook, the email returned as part of user_detailed_info is not a valid string. It is a null string? To Reproduce Click the "Create your Saythanks inbox" button Click on "Sign up with Facebook" The authentication happens successfully. Send a note by clicking on the "Say Thanks!" link. Edit and send a note. Expected behaviour The note will get created and stored in the DB The email to the userid will fail as captured in the logfile on the server (see screenshot below) Screenshots
Technical improvement Use djlint to reformat the template files (*.htm.j2) in the project.
Is your feature request related to a problem? Please describe. The current template for the email being delivered is too airy; too much white spaces. Allow the user to define her own template and use that instead. Describe the solution you'd like A set of pre-defined templates can be given to the the user, providing some semblance of a choice. Additional context See below. An example of a different TEMPLATE that rendered the email more elgantly!
Describe the bug When visiting any URL, the connection attempts for some while then eventually some backend times out and the webserver returns 504 Gateway Time-out openresty for all URLs To Reproduce Steps to reproduce the behaviour: Browse to https://saythanks.io/ Expected behaviour The site should come up Screenshots
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 BlitzKraft/saythanks.io, 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 BlitzKraft/saythanks.io acknowledge new external contributions in approximately 5 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 88.9% were successfully merged into the primary branch.
BlitzKraft/saythanks.io has a recorded first-timer success rate of 60.0%. Repositories ranked Elite 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 73.2 places BlitzKraft/saythanks.io in the Elite tier.
The external pull request merge rate is 88.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, BlitzKraft/saythanks.io currently has 5 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for BlitzKraft/saythanks.io 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.