SASTOpen source · Apache-2.0
Bandit
Community project
A free, Python-specific static analysis linter that walks a codebase's abstract syntax tree looking for common security mistakes — hardcoded passwords, use of insecure functions, SQL string construction. Governed by PyCQA (the Python Code Quality Authority) rather than any single company, and a frequent building block inside larger CI security pipelines.
Verified Source: 1
- Product type
- Community project
- Deployment
- CLI
- Organization size
- IndividualSMBMid-marketEnterprise
- Pricing tier
- Free
Capability checklist
SASTHow Bandit measures up against the full Static Application Security Testing taxonomy.
- Source code vulnerability scanning — supported
- Analyzes source code for security flaws without executing the application.
- IDE & CI/CD integration — supported
- Surfaces findings directly in the developer's editor or pull request.
- Language & framework coverage — not supported
- Breadth of programming languages and frameworks the scanner understands.
- False-positive triage & prioritization — not supported
- Ranks and filters findings so developers focus on the issues that matter.
- Secrets detection — not supported
- Flags hardcoded credentials, API keys, and tokens committed to source code.
- Custom rule authoring — not supported
- Lets teams write organization-specific detection rules beyond the built-in set.
- PR / commit gating — not supported
- Blocks merges when new high-severity findings are introduced.
- IaC & container config scanning — not supported
- Scans infrastructure-as-code templates and container configurations for misconfigurations alongside application code.
Alternatives
Other Static Application Security Testing tools with overlapping capabilities, sized for similar teams.
Appears in stacks
Real-world stacks that include Bandit.