Skip to content
Back to search

wemake-python-styleguide

The strictest and most opinionated Python linter ever

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/wemake-services/wemake-python-styleguide with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/wemake-services/wemake-python-styleguide'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/wemake-services--wemake-python-styleguide/badge.svg)](/listings/wemake-services--wemake-python-styleguide)

HTML

<a href="/listings/wemake-services--wemake-python-styleguide"><img src="/api/listings/wemake-services--wemake-python-styleguide/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

pip install wemake-python-styleguide

You will also need to create a `setup.cfg` file with the [configuration](https://wemake-python-styleguide.rtfd.io/en/latest/pages/usage/configuration.html).

[Try it online](https://wps.orsinium.dev)!

We highly recommend to also use:

- [ondivi](https://wemake-python-styleguide.rtfd.io/en/latest/pages/usage/integrations/ondivi.html) for easy integration into a **legacy** codebase

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 31 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "wemake-python-styleguide",
  3. "version": "1.0.0",
  4. "owner": {
  5. "name": "wemake-services"
  6. },
  7. "description": "The strictest and most opinionated Python linter ever",
  8. "plugins": [
  9. {
  10. "name": "wps",
  11. "source": "./wemake_python_styleguide/.agents/skills/wps",
  12. "description": "Write code that passes wemake-python-styleguide",
  13. "author": {
  14. "name": "wemake-services",
  15. "url": "https://github.com/wemake-services"
  16. },
  17. "license": "MIT",
  18. "homepage": "https://wemake-python-styleguide.readthedocs.io",
  19. "repository": "https://github.com/wemake-services/wemake-python-styleguide",
  20. "keywords": [
  21. "flake8",
  22. "flake8-plugin",
  23. "linter",
  24. "python",
  25. "code-quality",
  26. "styleguide",
  27. "wemake-python-styleguide"
  28. ]
  29. }
  30. ]
  31. }
README.md · README · 181 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # wemake-python-styleguide
  2. [![wemake.services](https://img.shields.io/badge/%20-wemake.services-green.svg?label=%20&logo=data%3Aimage%2Fpng%3Bbase64%2CiVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAMAAAAoLQ9TAAAABGdBTUEAALGPC%2FxhBQAAAAFzUkdCAK7OHOkAAAAbUExURQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAP%2F%2F%2F5TvxDIAAAAIdFJOUwAjRA8xXANAL%2Bv0SAAAADNJREFUGNNjYCAIOJjRBdBFWMkVQeGzcHAwksJnAPPZGOGAASzPzAEHEGVsLExQwE7YswCb7AFZSF3bbAAAAABJRU5ErkJggg%3D%3D)](https://wemake-services.github.io)
  3. [![Supporters](https://img.shields.io/opencollective/all/wemake-python-styleguide.svg?color=gold&label=supporters)](https://opencollective.com/wemake-python-styleguide)
  4. [![test](https://github.com/wemake-services/wemake-python-styleguide/actions/workflows/test.yml/badge.svg?branch=master&event=push)](https://github.com/wemake-services/wemake-python-styleguide/actions/workflows/test.yml)
  5. [![codecov](https://codecov.io/gh/wemake-services/wemake-python-styleguide/branch/master/graph/badge.svg)](https://codecov.io/gh/wemake-services/wemake-python-styleguide)
  6. [![Python Version](https://img.shields.io/pypi/pyversions/wemake-python-styleguide.svg)](https://pypi.org/project/wemake-python-styleguide/)
  7. [![wemake-python-styleguide](https://img.shields.io/badge/style-wemake-000000.svg)](https://github.com/wemake-services/wemake-python-styleguide)
  8. ---
  9. Welcome to the strictest and most opinionated Python linter ever.
  10. *The best tool to teach your LLM how to write idiomatic and simple Python code!*
  11. <p align="center">
  12. <a href="https://wemake-python-styleguide.rtfd.io">
  13. <img src="https://raw.githubusercontent.com/wemake-services/wemake-python-styleguide/master/docs/_static/logo.png"
  14. alt="wemake-python-styleguide logo">
  15. </a>
  16. </p>
  17. `wemake-python-styleguide` is actually a [flake8](http://flake8.pycqa.org/en/latest/)
  18. plugin, the only one you will need as your [ruff](https://github.com/astral-sh/ruff) companion.
  19. Fully compatible with **ALL** rules and format conventions from `ruff`.
  20. ## Quickstart
  21. ```bash
  22. pip install wemake-python-styleguide
  23. ```
  24. You will also need to create a `setup.cfg` file with the [configuration](https://wemake-python-styleguide.rtfd.io/en/latest/pages/usage/configuration.html).
  25. [Try it online](https://wps.orsinium.dev)!
  26. We highly recommend to also use:
  27. - [ondivi](https://wemake-python-styleguide.rtfd.io/en/latest/pages/usage/integrations/ondivi.html) for easy integration into a **legacy** codebase
  28. ## AI Features
  29. `wemake-python-styleguide` works natively with AI tools,
  30. it is great for improving agents' code quality.
  31. Skills:
  32. - [`/wps`](https://github.com/wemake-services/wemake-python-styleguide/blob/master/wemake_python_styleguide/.agents/skills/wps/SKILL.md) to run better Python code that passes `wemake-python-styleguide`. Install in Claude Code: `/plugin install wps --marketplace wemake-services/wemake-python-styleguide`
  33. MCPs:
  34. - [wps](https://wemake-python-styleguide.readthedocs.io/en/latest/pages/usage/cli.html#mcp) MCP helps with explaining violations and provides context on how to fix them
  35. Additional contexts for LLMs:
  36. - [Context7](https://context7.com/wemake-services/wemake-python-styleguide)
  37. - [`llms.txt`](https://wemake-python-styleguide.readthedocs.io/llms.txt)
  38. - [`llms-full.txt`](https://wemake-python-styleguide.readthedocs.io/llms-full.txt)
  39. See full [AI docs](https://wemake-python-styleguide.readthedocs.io/en/latest/pages/usage/cli.html).
  40. ## Running
  41. ```bash
  42. flake8 your_module.py --select=WPS
  43. ```
  44. This app is still just good old `flake8`!
  45. And it won't change your existing workflow.
  46. <p align="center">
  47. <img src="https://raw.githubusercontent.com/wemake-services/wemake-python-styleguide/master/docs/_static/running.png"
  48. alt="invocation results">
  49. </p>
  50. See ["Usage" section](https://wemake-python-styleguide.rtfd.io/en/latest/pages/usage/setup.html)
  51. in the docs for examples and integrations.
  52. We also support [GitHub Actions](https://wemake-python-styleguide.rtfd.io/en/latest/pages/usage/integrations/github-actions.html) as first class-citizens.
  53. [Try it out](https://github.com/marketplace/actions/wemake-python-styleguide)!
  54. Can (and should!) be used with `ruff`:
  55. ```bash
  56. ruff check && ruff format
  57. flake8 . --select=WPS
  58. ```
  59. See example `ruff` configuration in our [`pyproject.toml`](https://github.com/wemake-services/wemake-python-styleguide/blob/master/pyproject.toml#L103).
  60. ## Strict is the new cool
  61. Strict linting offers the following benefits to developers and companies:
  62. 1. Ensures consistency - no matter who works on it, the end product will always be the same dependable code
  63. 2. Helps avoid potential bugs - strict rules make sure that you don't make common mistakes
  64. 3. Efficient code reviews - each piece of code has a similar familiar style and syntax. If it passes all the checks, there's little left to review!
  65. 4. Fewer code revisions - strict linting ensures that you don't have to re-write the codebase again and again
  66. 5. Reduce code redundancy - Sometimes we write complex code as we are thinking in a certain way about a problem. The linter offers suggestions that can help simplify the code and eliminate redundant statements
  67. ## What we are about
  68. The ultimate goal of this project is
  69. to make all people write **exactly** the same `Python` code.
  70. | | flake8 | pylint | black | mypy | ruff | wemake-python-styleguide |
  71. |----------------------------|--------|--------|-------|------|------|--------------------------|
  72. | Formats code? | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ |
  73. | Finds style issues? | 🤔 | ✅ | 🤔 | ❌ | ✅ | ❌ |
  74. | Finds bugs? | 🤔 | ✅ | ❌ | ✅ | ✅ | ✅ |
  75. | Finds complex code? | ❌ | 🤔 | ❌ | ❌ | ❌ | ✅ |
  76. | Has a lot of strict rules? | ❌ | 🤔 | ❌ | ❌ | ✅ | ✅ |
  77. | Has a lot of plugins? | ✅ | ❌ | ❌ | 🤔 | ❌ | ✅ |
  78. We have several primary objectives:
  79. 1. Significantly reduce the complexity of your code and make it more maintainable
  80. 2. Enforce "There should be one -- and preferably only one -- obvious way to do it" rule to coding and naming styles
  81. 3. Protect developers from possible errors and enforce best practices
  82. You can find all error codes and plugins [in the docs](https://wemake-python-styleguide.rtfd.io/en/latest/pages/usage/violations/index.html).
  83. ## What we are not
  84. We are *not* planning to do the following things:
  85. 0. Assume or check types, use `mypy` together with our linter
  86. 1. Format code or produce stylistic errors, use `ruff format` for that
  87. 2. Check for all kinds of logical bugs, write tests instead
  88. 3. Appeal to everyone. But, you can [switch off](https://wemake-python-styleguide.rtfd.io/en/latest/pages/usage/setup.html#ignoring-violations) any rules that you don't like
  89. ## Supporting us :tada:
  90. We in [wemake.services](https://github.com/wemake-services) make
  91. all our tools open-source by default, so the community can benefit from them.
  92. If you use our tools and they make your life easier and brings business value,
  93. you can return us a favor by supporting the work we do.
  94. [![Gold Tier](https://opencollective.com/wemake-python-styleguide/tiers/gold-sponsor.svg?width=890)](https://opencollective.com/wemake-python-styleguide)
  95. [![Silver Tier](https://opencollective.com/wemake-python-styleguide/tiers/silver-sponsor.svg?width=890&avatarHeight=45&button=0)](https://opencollective.com/wemake-python-styleguide)
  96. [![Bronze Tier](https://opencollective.com/wemake-python-styleguide/tiers/bronze-sponsor.svg?width=890&avatarHeight=35&button=0)](https://opencollective.com/wemake-python-styleguide)
  97. ## Show your style :sunglasses:
  98. If you use our linter - it means that your code is awesome.
  99. You can be proud of it!
  100. And you should share your accomplishment with others
  101. by including a badge in your `README` file. It looks like this:
  102. [![wemake-python-styleguide](https://img.shields.io/badge/style-wemake-000000.svg)](https://github.com/wemake-services/wemake-python-styleguide)
  103. ### Markdown
  104. ```md
  105. [![wemake-python-styleguide](https://img.shields.io/badge/style-wemake-000000.svg)](https://github.com/wemake-services/wemake-python-styleguide)
  106. ```
  107. ### Restructured text
  108. ```rst
  109. .. image:: https://img.shields.io/badge/style-wemake-000000.svg
  110. :target: https://github.com/wemake-services/wemake-python-styleguide
  111. ```
  112. ## Contributing
  113. We **warmly welcome** all contributions!
  114. [![List of contributors](https://opencollective.com/wemake-python-styleguide/contributors.svg?width=890&button=0)](https://github.com/wemake-services/wemake-python-styleguide/graphs/contributors)
  115. See ["Contributing"](https://wemake-python-styleguide.rtfd.io/en/latest/pages/api/index.html#contributing) section in the documentation if you want to contribute.
  116. You can start with [issues that need some help](https://github.com/wemake-services/wemake-python-styleguide/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22)
  117. right now.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.