Analysis updated 2026-07-17 · repo last pushed 2013-12-04
Run Pylama before committing to catch style and quality issues automatically.
Set up Pylama as a git hook to check every commit.
Integrate Pylama into a CI pipeline to enforce code quality across a team.
Write a custom linter plugin to check for project-specific rules.
| sethwoodworth/pylama | 0-bingwu-0/live-interpreter | 0xkaz/llm-governance-dashboard | |
|---|---|---|---|
| Stars | 2 | 2 | 2 |
| Language | Python | Python | Python |
| Last pushed | 2013-12-04 | — | — |
| Maintenance | Dormant | — | — |
| Setup difficulty | easy | moderate | hard |
| Complexity | 2/5 | 2/5 | 4/5 |
| Audience | developer | general | ops devops |
Figures from each repo's GitHub metadata at analysis time.
Pylama is a code quality checker that scans your Python and JavaScript files to find bugs, style issues, and code smells. Instead of running several different tools separately, it bundles multiple checkers together and shows you all the problems in one unified report. When you run Pylama on your codebase, it looks for things like formatting violations (spaces, indentation), naming problems, unused variables, overly complex functions, and other code quality issues. You get back a list of errors with line numbers and descriptions so you know exactly what to fix. You can customize which checks to run, which errors to ignore, and which files to skip, useful if you want to be strict about some files but lenient about others. The typical user is a Python developer or team lead who wants to keep code quality consistent across a project. You might run it before committing code, set it up as a git hook to check every commit automatically, or integrate it into your CI pipeline to catch issues early. For example, a startup could add Pylama to their codebase to enforce consistent style across a growing team without requiring manual code review for formatting problems. Pylama is built as a wrapper around several well-known Python linters, PEP8, PyFlakes, McCabe, and others, so you get the benefits of established tools without learning separate commands for each. You can also write your own custom linter as a plugin if you need to check for something domain-specific to your project. The tool is configured via a simple ini file, so your team's rules stay consistent across developers and machines.
A code quality checker that bundles multiple Python linters into one tool, reporting style issues, bugs, and code smells in a single unified report.
Mainly Python. The stack also includes Python, PEP8, PyFlakes.
Dormant — no commits in 2+ years (last push 2013-12-04).
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.