wemake-services/wemake-python-styleguide - Open Source PR Review Scorecard

The strictest and most opinionated python linter ever!

C-Rank Grade: S (Elite) - 70/100

External PR Merge Rate: 95%

Response Time: -

First Timer Success: 100%

Frequently Asked Questions

Is wemake-services/wemake-python-styleguide welcoming to first-time open-source contributors?

wemake-services/wemake-python-styleguide has a recorded first-timer success rate of 100.0%. Repositories ranked S 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 wemake-services/wemake-python-styleguide respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 69.6 C-Rank™ score (S 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 69.6 places wemake-services/wemake-python-styleguide in the S tier.

What is the external contributor pull request merge rate for wemake-services/wemake-python-styleguide?

The external contributor pull request merge rate for wemake-services/wemake-python-styleguide is 95.2%, based on public PR activity from non-core contributors.

Are there Good First Issues available in wemake-services/wemake-python-styleguide?

wemake-services/wemake-python-styleguide currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

wemake-services
wemake-services/wemake-python-styleguideS•Elite2.9k
GitHub
Back to Explorer
wemake-services

wemake-services/wemake-python-styleguide

2,926
Active (30d)S•Elite(70/100)Python

The strictest and most opinionated python linter ever!

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Maintainer

Warmth Score
7.8/10
Patience Score
8.2/10
Nitpick Rate
20%

Active Python repository in wemake-services/wemake-python-styleguide with ongoing community development and issue triage.

Top PR Submission Do's

  • •Ensure code complies with Python style conventions
  • •Keep PRs scoped and well-documented

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without context
  • •Do not break existing automated test suites
Response Velocity
-
No reviewer activity recorded

Average Response Latency

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

Merge Efficiency
95.2%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
4 core
Small core review team
Diagnostic Health HUD
95.2%
Merge Gauge
100.0%
1st-Timer
Community Vibe68/100

Embed C-Rank Badge

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

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

Active Good First Issues (4)

View on GitHub

What's wrong ~/ruff-ex poetry add wemake-python-styleguide Using version ^1.8.1 for wemake-python-styleguide Updating dependencies Resolving dependencies... (1.7s) Package operations: 7 installs, 0 updates, 0 removals - Installing mccabe (0.7.0) - Installing pycodestyle (2.15.0) - Installing pyflakes (4.0.3) - Installing attrs (26.1.0) - Installing pygments (2.21.0) - Installing flake8 (7.4.1) - Installing wemake-python-styleguide (1.8.1) Writing lock file ~/ruff-ex wps explain WPS211 zsh: command not found: wps ~/ruff-ex poetry run wps explain WPS211 Traceback (most recent call last): File "/Users/khabibshahbanov/Library/Caches/pypoetry/virtualenvs/ruff-ex-wlM0JbiC-py3.15/bin/wps", line 5, in <module> from wemake_python_styleguide.cli.cli_app import main File "/Users/khabibshahbanov/Library/Caches/pypoetry/virtualenvs/ruff-ex-wlM0JbiC-py3.15/lib/python3.15/site-packages/wemake_python_styleguide/cli/cli_app.py", line 3, in <module> from wemake_python_style

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

move _formatted_string_parts to logic part Originally posted by @sobolevn in #3822 (review)

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

I can't limit the number of types I import from typing, I can't refactor types to use typing. prefix and import import typing We need to just ignore this module. And typing_extensions as well.

📅 Opened Sep 27, 2026💬 1 comment
Quality: 75/100Contribute

These two lines: tuple(f'/{pref.strip("/")}/' for pref in (prefix, *prefixes)) tuple(f'/{pref.strip("/")}' for pref in (prefix, *prefixes)) (notice the missing / at the end) have different Jones complexity. They must not. It should be counted as: 1 per every {} As regular for all python expressions inside {} All string parts of fstring are counted as total of 1

📅 Opened Sep 25, 2026💬 0 comments
Quality: 90/100Contribute
Looking for more Python beginner tasks?Explore Python 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 wemake-services/wemake-python-styleguide

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

Frequently Asked Questions - Contributing to wemake-services/wemake-python-styleguide

01

Is wemake-services/wemake-python-styleguide welcoming to first-time open-source contributors?

wemake-services/wemake-python-styleguide has a recorded first-timer success rate of 100.0%. Repositories ranked Elite 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 ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 69.6 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 69.6 places wemake-services/wemake-python-styleguide in the Elite tier.

04

What is the external contributor pull request merge rate for wemake-services/wemake-python-styleguide?

The external pull request merge rate is 95.2%. 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 wemake-services/wemake-python-styleguide?

Yes, wemake-services/wemake-python-styleguide currently has 1 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 wemake-services/wemake-python-styleguide 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.