pycqa/flake8

flake8 is a python tool that glues together pycodestyle, pyflakes, mccabe, and third-party plugins to check the style and quality of some python code.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 minute ago
Added to GitGenius on September 18th, 2026
Created on September 13th, 2014
Open Issues & Pull Requests: 23 (+0)
GitHub issues: Enabled
Number of forks: 356
Total Stargazers: 3,823 (+0)
Total Subscribers: 37 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.4 hours
Mean response time: 64.5 days
90th percentile: 3.0 days
Tracked items: 49

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 8
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,590 days
Stale 30+ days: 8
Stale 90+ days: 5

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • feature:accepted (2)
  • priority:medium (2)
  • bug:confirmed (1)
  • component:docs (1)
  • component:legacy-api (1)
  • confirmed-by:core (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

flake8 is a Python linter that wraps together PyFlakes, pycodestyle, and McCabe complexity analysis to check code style and quality in a single command.

The tool solves the problem of running multiple Python code checkers separately by unifying them into one interface. It aggregates warnings from style checkers, logical error detection, and complexity analysis, then displays them in merged per-file output. Beyond combining these tools, flake8 adds practical features like the ability to skip entire files with a flake8: noqa comment, suppress warnings on specific lines with # noqa annotations, ignore particular error codes selectively, and integrate with Git and Mercurial hooks.

flake8 suits any Python project that wants straightforward style and quality enforcement without managing multiple linting tools. It works well for teams adopting PEP 8 standards and for projects that need both style compliance and basic logical error detection. The tool is extensible through entry points, allowing third-party plugins to add custom checks or formatting rules, which makes it adaptable to projects with specific linting requirements beyond the built-in checks.

The project maintains active continuous integration with automated testing on each change. It engages with its community through a dedicated Discord server and a mailing list for questions and feature discussions. The tool is integrated into pre-commit.ci for automated checking in pull request workflows, indicating ongoing compatibility with modern development practices.