# vulture を Homebrew, apt, MacPorts, pacman でインストール vulture のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。 ## インストール ```sh sudo av install brew:vulture ``` 追加のインストールコマンド: ### macOS - Homebrew (100%): ```sh brew install vulture ``` 証拠: local Homebrew formula metadata - MacPorts (94%): ```sh sudo port install vulture ``` 証拠: MacPorts ports tree: devel/vulture/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 ### Linux - Debian apt (92%): ```sh sudo apt install vulture ``` 証拠: Debian stable package indexes: vulture from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz - pacman (92%): ```sh sudo pacman -S vulture ``` 証拠: Arch Linux sync databases: vulture from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz ## パッケージ情報 - **パッケージキー:** brew:vulture - **パッケージマネージャ:** Homebrew - **バージョン:** 2.16 - **ソース概要:** Find dead Python code - **ホームページ:** - **リポジトリ:** - **生成日時:** 2026-08-03T19:37:03+00:00 ## 実行可能ファイル - vulture (エイリアス) ## インストール挙動 - Bottle: 利用不可 ## バージョンと鮮度 - ページ生成日: 2026-08-03 - マネージャ版: 2.16 ## プロジェクトの歴史と使われ方 Vulture is a Python static-analysis command-line tool for finding unused code. It scans Python files, records defined and used names with the standard-library `ast` module, reports likely unused imports, variables, functions, methods, classes, properties, attributes, and also detects some unreachable code. ### プロジェクトの歴史 Vulture has a longer history than its current GitHub repository suggests: PyPI records version 0.1 uploaded on March 17, 2012. The current GitHub repository was created in March 2017 under maintainer Jendrik Seipp, and the package metadata continues to identify him as the author/owner. The project matured from a small dead-code finder into a production/stable Python quality tool. Its README emphasizes that Python's dynamic nature makes perfect static dead-code detection impossible, so Vulture reports confidence values and provides practical suppression mechanisms rather than pretending to be exact. The 2.x series made Vulture fit modern Python project workflows: it supports `pyproject.toml` configuration, pre-commit integration, programmatic use, whitelists for false positives, common whitelists in the repository, and output syntax that complements Pyflakes. ### 採用の歴史 Vulture became a recognizable tool in Python maintenance circles because it addresses a recurring problem in large, long-lived codebases: unused helpers, stale imports, abandoned feature paths, and untested code that ordinary linting or test coverage may not make obvious. By July 2026, GitHub repository metadata showed more than 4.6k stars, and PyPI listed Vulture 2.16 as the current release, uploaded on March 25, 2026. It also appears in editor and automation workflows through pre-commit hooks, a GitHub Action, and VS Code extension integrations. ### 使われ方 Typical usage is `vulture path_or_file`, optionally with directories, a generated whitelist, and a confidence threshold such as `--min-confidence 100`. The tool recommends scanning both a library and its test suite so code used only by tests is seen as used, and then rerunning after deletions because removing one chunk can reveal more dead code. Vulture's confidence model is part of its identity. It treats unreachable code and unused function or method arguments as 100 percent, imports as 90 percent, and many attributes, classes, functions, methods, properties, and variables as 60 percent. Users tune results with whitelists, excludes, ignored names or decorators, `noqa` compatibility for selected Pyflakes codes, and `pyproject.toml` settings. ### パッケージ好きにとっての重要性 For package nerds, Vulture is the small sharp tool between linting and coverage. It is simpler than a whole quality platform, depends mostly on Python's parser, and is valuable in cleanup branches, CI gates, and pre-commit checks where the goal is to find deletion candidates before they fossilize. ### タイムライン - 2012: Vulture 0.1 was uploaded to PyPI on March 17, 2012. - 2017: The current GitHub repository was created on March 6, 2017. - 2021: Vulture 2.3 appeared as the example pre-commit hook revision in the README's integration documentation. - 2026: Vulture 2.16 was uploaded to PyPI on March 25, 2026. ### Related projects - Vulture is related to Pyflakes, Flake8, Coverage.py, pre-commit, Ruff discussions around dead-code detection, editor extensions that wrap Vulture, and other Python dead-code tools such as uncalled and dead. ### ソース - - - - - - ## セキュリティノート 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: pyproject.toml ## 他のパッケージマネージャ記録 - Debian apt - vulture - 2.14-1: normalized package name match | Debian stable package indexes: vulture from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | scans for unused ("dead") code in a Python program | https://github.com/jendrikseipp/vulture - Ubuntu apt - vulture - 2.7-2: normalized package name match | Ubuntu 24.04 LTS package indexes: vulture from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | scans for unused ("dead") code in a Python program | https://github.com/jendrikseipp/vulture - pacman - vulture - 2.16-1: normalized package name match | Arch Linux sync databases: vulture from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | Finds dead code in Python projects | https://github.com/jendrikseipp/vulture - MacPorts - vulture: normalized package name match | MacPorts ports tree: devel/vulture/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 ## Combined YAML source View the package source record on GitHub. [combined/vulture.yml](https://github.com/mxcl/pkgdb/blob/main/combined/vulture.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