oxsecurity / megalinter

# MegaLinter, by 
MegaLinter is an **open-source** tool for **CI/CD workflows** that analyzes the **consistency of your code**, **IaC**, **configuration**, and **scripts** in your repository to **ensure all your project sources are clean and formatted**, no matter which IDE or toolbox is used by your developers. Powered by **OX Security**.
Supports **67** languages, **23** formats, **22** tooling formats, and is **ready to use out of the box** as a GitHub Action or with any CI system. It is **highly configurable** and **free for all uses**.
MegaLinter has **native integrations** with popular CI/CD tools and is compliant with most **Coding Agents**.
- Use the new LLM Advisor that will tell you how to fix linters issues
- Create your own MegaLinter Custom Flavors to improve performance
Before you go further, see the **online documentation website, which offers much easier navigation than this README**
## Table of Contents
- Why MegaLinter
- Quick Start
- Coding Agents
- Supported Linters
 - Languages
 - Formats
 - Tooling formats
 - Other
- Installation
 - Coding agents (skills)
 - Coding Agents (Plugins)
 - Assisted installation
 - Which version to use ?
 - GitHub Action
 - GitLab CI
 - Azure Pipelines
 - Single Repository
 - Central Repository
 - Pull Request Comments
 - Detailed Tutorial
 - Bitbucket Pipelines
 - Jenkins
 - Concourse
 - Pipeline step
 - Use it as a reusable task
 - Drone CI
 - (Optional) Adjusting trigger rules
 - Docker container
 - Run MegaLinter locally
- Configuration
 - .mega-linter.yml file
 - Common variables
 - Activation and deactivation
 - Filter linted files
 - Apply fixes
 - Apply fixes issues
 - Notes
 - Linter specific variables
 - Pre-commands
 - Post-commands
 - Environment variables security
 - Secured env variables
 - Secured configuration examples
 - Default secured variables
 - Unhide variables for linters
 - CLI lint mode
- Reporters
- Flavors
- Badge
 - Markdown
 - reStructuredText
- Plugins
 - External Plugins Catalog
 - Use external plugins
 - Example
 - Create your own plugin
 - Limitations
- They talk about MegaLinter
 - English articles
 - French articles
 - Videos
 - Web Sites
 - Linters
- Frequently Asked Questions
- How to contribute
- Special thanks
 - Maintainers
 - Contributors
 - Open-source teams
 - Super-Linter team
- License
- MegaLinter vs Super-Linter
 - Security
 - Performance
 - More languages and formats linted
 - Automatically apply formatting and fixes
 - Run locally
 - Reports
 - Capabilities
 - Additional Reporters
 - Enhanced configuration
 - Enhanced documentation
 - Plugin management
 - Simplify architecture and evolutionary maintenance
 - Improve robustness \& stability
## Why MegaLinter
Projects need to contain clean code in order to **avoid technical debt**, which makes **ongoing maintenance harder and more time-consuming**.
By using **code formatters and code linters**, you ensure that your **codebase is easier to read** and **follows best practices**, from kickoff through eac