# flake8 を Homebrew, apt, pacman でインストール flake8 のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。 ## インストール ```sh sudo av install brew:flake8 ``` 追加のインストールコマンド: ### macOS - Homebrew (100%): ```sh brew install flake8 ``` 証拠: local Homebrew formula metadata ### Linux - Debian apt (92%): ```sh sudo apt install flake8 ``` 証拠: Debian stable package indexes: flake8 from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz - pacman (92%): ```sh sudo pacman -S python-flake8 ``` 証拠: Arch Linux sync databases: python-flake8 from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz ## パッケージ情報 - **パッケージキー:** brew:flake8 - **パッケージマネージャ:** Homebrew - **バージョン:** 7.3.0 - **ソース概要:** Lint your Python code for style and logical errors - **ホームページ:** - **リポジトリ:** - **生成日時:** 2026-08-03T19:37:03+00:00 ## 実行可能ファイル - flake8 (エイリアス) ## インストール挙動 - Bottle: 利用不可 ## バージョンと鮮度 - ページ生成日: 2026-08-03 - マネージャ版: 7.3.0 ## プロジェクトの歴史と使われ方 flake8 is a Python style and quality checker that glues together pycodestyle, PyFlakes, McCabe complexity checks, and third-party plugins. Its official documentation presents it as a command-line tool for checking files or directories and as a configurable platform for Python linting policy. ### プロジェクトの歴史 The recorded release history begins with the 0.x series; the 0.6 release in February 2010 fixed McCabe metric handling, and 1.0 followed in November 2011 with complexity-checking changes. The project later moved under PyCQA, whose official repository describes flake8 as a tool that combines pycodestyle, pyflakes, mccabe, and plugins. The 3.0.0 release in July 2016 was a major internal and documentation rewrite. Its notes say the project removed dependence on pep8/pycodestyle for file processing and plugin dispatch while keeping compatibility, added formatter entry points, improved plugin option registration, changed hook installation behavior, and rewrote documentation at flake8.pycqa.org. ### 採用の歴史 flake8 became popular because it packaged several Python code-quality checks behind one command and one set of configuration files. The official plugin guide explicitly attributes much of its popularity to extensibility and notes that community plugins are typically distributed on PyPI. In day-to-day Python packaging, flake8 is commonly installed into the same Python environment that should parse the target code. The docs warn that Flake8 is tied to the Python version on which it runs, because it must understand that version's syntax. ### 使われ方 The basic workflow is `flake8 path/to/code.py` or `flake8 path/to/code/`, optionally with selection and ignore flags for specific error codes. The user guide documents project configuration in `setup.cfg`, `tox.ini`, or `.flake8`, all using a `[flake8]` INI section. Plugins extend checks and formatters. After installation, most plugins immediately start reporting their own codes, and some register additional command-line or configuration options. ### パッケージ好きにとっての重要性 flake8 matters to package nerds because it became the small, composable linting facade for a large slice of Python packaging: pycodestyle contributes E/W codes, PyFlakes contributes F codes, McCabe contributes C codes, and plugins add their own namespaces. Its configuration-file search and plugin entry-point model made it easy for projects, tox environments, pre-commit hooks, and distribution packages to agree on one executable while still carrying local policy. ### タイムライン - 2010: 0.6 release recorded in official release notes. - 2011: 1.0 release changes default complexity-checking behavior. - 2016: 3.0.0 rewrites documentation, file processing, plugin dispatch, and formatter extension points. - 2020s: 7.x release series appears in the official release history. ### Related projects - pycodestyle supplies PEP 8 style checks and E/W error-code classes. - PyFlakes supplies lint checks such as unused imports and F error codes. - McCabe supplies complexity checks and C error codes. - Third-party flake8 plugins distributed through PyPI add checks and formatters. ### ソース - - - - - ## セキュリティノート narrow executable package without higher-risk signals. - **Geiger リスク:** グリーン / 低 - narrow executable package without higher-risk signals ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: setup.cfg, tox.ini, .flake8 ## 他のパッケージマネージャ記録 - Debian apt - flake8 - 7.1.1-3: normalized package name match | Debian stable package indexes: flake8 from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | code checker using pycodestyle and pyflakes | https://github.com/pycqa/flake8 - Ubuntu apt - flake8 - 7.0.0-1: normalized package name match | Ubuntu 24.04 LTS package indexes: flake8 from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | code checker using pycodestyle and pyflakes | https://github.com/pycqa/flake8 - pacman - python-flake8 - 1:7.3.0-2: normalized package name match | Arch Linux sync databases: python-flake8 from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | The modular source code checker: pep8, pyflakes and co | https://flake8.pycqa.org ## Combined YAML source View the package source record on GitHub. [combined/flake8.yml](https://github.com/mxcl/pkgdb/blob/main/combined/flake8.yml) ## ソース - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph