A compilation of sites with dumb password rules.
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 89%
Response Time: 2h
First Timer Success: 100%
duffn/dumb-password-rules 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 duffn/dumb-password-rules respond to incoming external pull requests in approximately 1.8 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 58.9 places duffn/dumb-password-rules in the A tier.
The external contributor pull request merge rate for duffn/dumb-password-rules is 88.9%, based on public PR activity from non-core contributors.
duffn/dumb-password-rules currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
A compilation of sites with dumb password rules.
Collaborative maintainer environment in duffn/dumb-password-rules. Reviews community pull requests with focus on project quality.
Discussions in duffn/dumb-password-rules 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/duffn/dumb-password-rules?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 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~9 hours (40% approval). Keep your diff compact for rapid review.
https://play.google.com/store/apps/details?id=fr.sesamvitale.cartevitale.app 10 chars at least (19 maximum) For a safe password, you need: 1 lowercase letter (a-z) 1 uppercase letter (A-Z) 1 special char (@?/* ...) 1 digit (0-9) No character input 3 times in a row But the better is yet to come: you have to enter that password using an in app keyboard, obviously poorly designed: to enter an uppercase letter, you have to use caps lock (switch to the uppercase layer, enter your letter and manually switch back to the lowercase layer) backspace key placement is unnaturral cannot move cursor; to correct a typo, you need to erase everything up to it you cannot paste in the password input you cannot use a password manager for this you may reveal the password field but you have to hold the button to keep it revealed you must input that password twice but the confirmation input isn't on the same screen: if you need to reveal the password field when entering the confirmation, you have to
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 duffn/dumb-password-rules, 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 duffn/dumb-password-rules acknowledge new external contributions in approximately 1 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.
duffn/dumb-password-rules 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 ~1 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 58.9 places duffn/dumb-password-rules in the Welcoming 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, duffn/dumb-password-rules 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 duffn/dumb-password-rules 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.