# Chargate > Security + lint gate — a thin MegaLinter wrapper with net-new (PR-diff) finding gating. Canonical documentation for Chargate, served at https://docs.magmamoose.com/chargate/. The full text of every page below is at `llms-full.txt`. Each link is the page's markdown. The page itself is the same address without the `index.md`, or with `.html` in place of `.md`. ## Docs - [Action reference](https://docs.magmamoose.com/chargate/action-reference/index.md): Every input and output of the magmamoose/chargate composite action, read from action.yml. For the task-shaped version with worked examples, see Setup and usage. For the CLI these inputs drive, see the CLI reference. - [Architecture](https://docs.magmamoose.com/chargate/architecture/index.md): Chargate is one chargate Python CLI (src/chargate/cli.py:main) behind two GitHub surfaces (a composite action and a pre-commit hook). The design splits cleanly into a pure core and a thin set of side-effecting edges. - [Token broker deployment](https://docs.magmamoose.com/chargate/broker-deployment/index.md): The broker exchanges a consumer's GitHub Actions OIDC token for a short-lived, repo-scoped Chargate[bot] installation token, so Chargate's PR comments carry that byline instead of github-actions[bot]. - [CLI reference](https://docs.magmamoose.com/chargate/cli/index.md): Both GitHub surfaces drive the same chargate CLI. Exit codes: 0 pass · 1 blocking net-new findings · 2 setup/usage error. - [Consuming the output](https://docs.magmamoose.com/chargate/consuming-output/index.md): Chargate classifies; the caller decides. Every run writes two documents another tool can read without importing any of Chargate: the net-new SARIF and the counts JSON. The counts JSON carries a schema_version and is a stable public interface — versioned, and broken only deliberately. - [Chargate](https://docs.magmamoose.com/chargate/index.md): Chargate is a security + lint gate built on MegaLinter. MegaLinter does all the scanning; Chargate adds the one thing that matters for day-to-day developer flow: net-new finding gating. - [What MegaLinter covers](https://docs.magmamoose.com/chargate/linter-coverage/index.md): Chargate v2 replaced a hand-rolled twelve-tool orchestration with MegaLinter. This page maps the old set onto what runs now — useful when migrating from v1, and when asking "is X still being scanned?" - [Net-new gating](https://docs.magmamoose.com/chargate/net-new/index.md): A SARIF result is net-new (and therefore gate-blocking) iff its primary location's file is in the PR diff and, at line precision, its startLine falls inside an added/modified hunk. The diff is computed against merge-base(base, head), which is robust to base-branch rebases and force-pushes. - [SAST direction: chargate vs CodeQL, engine or orchestrator?](https://docs.magmamoose.com/chargate/sast-benchmark/index.md): Status: decided · Decision: chargate is a SAST orchestrator/aggregator, not a competing analysis engine. It owns the ground CodeQL cedes (net-new PR-diff gating, cross-engine de-duplication, the DefectDojo/Dependency-Track bridge) and ingests CodeQL/Semgrep/KICS/checkov/hadolint SARIF rather than reimplementing… - [Security model](https://docs.magmamoose.com/chargate/security-model/index.md): Chargate is a security tool, so its own posture is part of the product. This page states what it assumes, what it grants, and what it deliberately cannot do. - [Setup & usage](https://docs.magmamoose.com/chargate/setup/index.md): On PRs it uses MegaLinter's focused security flavor and requests changed-files analysis, gates on net-new findings, and ships the full SARIF. Repository-level security scanners may still inspect the whole repo or history. On push to the default branch it runs a non-gating whole-repo baseline scan. Set flavor: all for… - [Troubleshooting](https://docs.magmamoose.com/chargate/troubleshooting/index.md): Symptom, cause, fix. Start with the exit code or the error string you actually saw.