pycqa/bandit

Bandit is a tool designed to find common security issues in Python code.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 4 minutes ago
Added to GitGenius on September 8th, 2026
Created on April 26th, 2018
Open Issues & Pull Requests: 259 (+0)
GitHub issues: Enabled
Number of forks: 833
Total Stargazers: 8,255 (+0)
Total Subscribers: 70 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 13.0 days
Mean response time: 193.1 days
90th percentile: 550.4 days
Tracked items: 91

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 86% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 4% of issues opened in the past year have been closed. Three people close 82% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 70
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 903 days
Stale 30+ days: 59
Stale 90+ days: 50

Recent activity

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

Top labels

  • bug (70)
  • enhancement (34)
  • good first issue (2)

Most active issues this week

Detailed Description

Bandit is a static security linter for Python code that identifies common security vulnerabilities through abstract syntax tree analysis.

Bandit addresses the need to catch security issues early in development by parsing Python source files into abstract syntax trees and running specialized plugins against the resulting nodes. This approach allows it to detect patterns indicative of security problems without executing the code. After scanning all files, it generates a report summarizing findings.

Bandit suits projects where security scanning is part of the development workflow, particularly those already using Python code quality tools from the PyCQA ecosystem. It works well integrated into continuous integration pipelines and is available as a container image supporting multiple architectures, making it deployable in containerized environments. The tool is appropriate for teams seeking automated detection of common security anti-patterns rather than deep manual security auditing.

The project maintains active continuous integration with automated testing on the main branch. Documentation is kept current and accessible through a dedicated documentation site. Container images are built and published through automated workflows with cryptographic verification available via sigstore cosign. The project accepts community contributions through a documented process and maintains communication channels for user engagement.