Docs
Install Radar, claim Free Preview or activate a paid license, then run the first local scan.
Direct answer
Install Radar, claim Free Preview or activate a paid license, then run the first local scan.
Getting started with Code Radar means installing the native CLI, claiming Free Preview or activating a license, then running `radar scan . --quick` on a real repository before changing team policy.
Start with `radar --version`, `radar activate --free --email <your-email>`, and `radar scan . --quick`. These commands keep implementation proof close to the repository instead of turning the docs page into a generic product description.
Confirm a local finding summary, report output, license status, and a clear next workflow for hooks, MCP, badges, or GitHub Actions. This evidence should be visible before moving from documentation to a paid or shared workflow.
Do not start with CI or checkout before the first local scan proves useful signal on real code. Next step: Move to install docs for setup details, local scan docs for report output, or pricing when repeat scans and CI slots are needed.
Content decision bridge
Readers on Getting started need a short route from answer-seeking to proof, rollout, and purchase evidence. Install Radar, claim Free Preview or activate a paid license, then run the first local scan.
Getting started should lead to product proof, not only more reading. For this page, proof means a first local scan on real code with inspectable findings.
Getting started becomes useful when the reader can repeat the workflow from the guide on a real repository. Here, rollout means a repeatable local scan, report, hook, or agent handoff.
Getting started should create a purchase path only when the product owns the next repeated job. For this intent, buying is justified by full local scans, exports, MCP, hooks, or repository validation.
Use the installer or build from source, claim the machine-bound Free Preview, then run the cockpit or an explicit scan.
# Get the current compatible signed installer at https://code-radar.dev/download/
radar --version
radar activate --free --email <your-email>
radar scan . --quickInstall a local hook, add MCP for agents, publish a README badge, and enable GitHub Actions when the repository needs CI enforcement.
radar hook install
radar prompt . --diff --copy
radar badgeConfirm the command, expected evidence, failure boundary, and next workflow before treating the task as complete.
Getting started with Code Radar means installing the native CLI, claiming Free Preview or activating a license, then running `radar scan . --quick` on a real repository before changing team policy.
Start with `radar --version`, `radar activate --free --email <your-email>`, and `radar scan . --quick`. These commands keep implementation proof close to the repository instead of turning the docs page into a generic product description.
Confirm a local finding summary, report output, license status, and a clear next workflow for hooks, MCP, badges, or GitHub Actions. This evidence should be visible before moving from documentation to a paid or shared workflow.
Do not start with CI or checkout before the first local scan proves useful signal on real code. Next step: Move to install docs for setup details, local scan docs for report output, or pricing when repeat scans and CI slots are needed.