Super-Linter
A bundle of many code linters that runs as a GitHub Action or in a container to check your code.
- Stars
- 10.6k
- Forks
- 1.1k
- Licence
- MIT
- Language
- Shell
- Last update
- 6 days ago
- Type
- Dev tool
What it is
Super-Linter is a ready-to-run collection of linters and code analyzers that checks source code for style and quality problems across many languages. It reports issues in the console and as GitHub Actions status checks, and it can also fix some formatting issues. Teams use it to keep code consistent without wiring up each tool separately.
- Run linters on every pull request and show results as GitHub status checks
- Run the same checks locally in a container before pushing code
- Automatically fix supported formatting issues using the built-in formatters
- Detect copy-pasted code blocks with the included jscpd tool
Great for
- Teams that want automated code checks on GitHub pull requests
- Projects spanning several programming languages that need one linting entry point
- Anyone who prefers running linters in a container instead of installing each tool locally
- Maintainers who want consistent formatting conventions enforced in CI
Not ideal for
- Projects not hosted on GitHub or not using a container runtime, since the README describes those as the main ways to run it
- People looking for a single language-specific linter, because it bundles many tools and may be heavier than needed
How to get it
- 1
Run with Docker
You'll need: Docker or another OCI-compatible container runtime (for standalone use)
Clone the repository
git clone https://github.com/super-linter/super-linter - 2
Run it
- Add the super-linter action to a GitHub workflow file, or run the container locally
- Let it scan your repository and read the console output or status checks
- Fix reported issues, or use the fix option for supported formatting problems
- 3
Get the most out of it
- Use the slim variant if you want a smaller image, as indicated by the slim-linterVersions.txt file in the release
- Review the supported linters table to confirm your languages are covered
- Read the development guide if you want to customize or contribute
Downloads
Strengths
- Bundles many linters and formatters for many languages in one tool
- Runs linters in parallel, per the README
- Released under the MIT license
Trade-offs
- Heavy: it ships many tools, and the README notes an image-size trade-off that it works to limit
- Configuration depends on the individual linters it includes, which you must learn to tune
How it compares
| Project | Stars | Type | Level | Updated | Best for |
|---|---|---|---|---|---|
| super-linter (this) | 10.6k | Dev tool | beginner | 6 days ago | Teams that want automated code checks on GitHub pull requests |
| SwiftLint | 19.8k | Dev tool | beginner | 20 days ago | iOS and macOS developers who want consistent Swift style across a team |
| static-analysis | 14.9k | Curated list | beginner | 4 days ago | Developers looking for a linter or analyzer for a specific language |
| act | 72.5k | Dev tool | intermediate | 5 days ago | Developers who edit .github/workflows files and want faster feedback than commit-and-push cycles |
| standard | 29.4k | Dev tool | beginner | 1.3 years ago | JavaScript projects where the team wants consistent style without debating rules |
| eslint | 27.6k | Dev tool | intermediate | 4 days ago | JavaScript developers who want automatic checks on their code |
Stats synced from GitHub. The assessment above was drafted with AI from the project's README on 2026-10-29 and may miss recent changes — check the README before relying on a command. MIT licence: free to use, modify and distribute, including commercially, as long as you keep the copyright notice.