jendrikseipp/vulture

Find dead Python code

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 22 minutes ago
Added to GitGenius on September 14th, 2026
Created on March 6th, 2017
Open Issues & Pull Requests: 71 (+0)
GitHub issues: Enabled
Number of forks: 202
Total Stargazers: 4,813 (+0)
Total Subscribers: 28 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 18.8 hours
Mean response time: 60.4 days
90th percentile: 151.8 days
Tracked items: 38

Most active contributors

Sign in to see contributor activity.

How this project is maintained

97% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 94% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 33
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 573 days
Stale 30+ days: 29
Stale 90+ days: 25

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Vulture is a static code analyzer that finds unused code in Python programs.

Vulture addresses the problem of identifying dead code in Python codebases through static analysis. Python's dynamic nature means that traditional static analyzers may miss some unused code or incorrectly flag code that is called implicitly, but Vulture still provides value by scanning for unused functions, classes, methods, variables, imports, and attributes. It assigns confidence values between 60% and 100% to each finding, indicating the likelihood that code is genuinely unused. This allows developers to filter results by confidence level, focusing first on certain dead code before investigating less certain cases.

Vulture suits developers maintaining large codebases who want to improve code quality and catch errors. It works well when run on both library code and test suites to identify untested functionality. The tool complements existing linters like pyflakes and uses the same output syntax, making it easy to integrate into existing workflows. The `--sort-by-size` option helps prioritize cleanup efforts by showing the largest unused code chunks first. For projects with many false positives, Vulture provides multiple suppression mechanisms: whitelists that can be generated automatically, file and directory exclusion patterns, and support for flake8 noqa comments.

The project maintains fast performance through static analysis and demonstrates high code quality with complete test coverage and self-testing. Development activity shows consistent attention to handling edge cases and user-reported issues, with particular focus on managing false positives through improved whitelist support and exclusion mechanisms. The maintainers actively curate whitelists for common Python modules and packages, accepting community contributions to expand coverage.