Install
Run the signed installer, then verify the native CLI.
radar --versionRun your first local scan now.
Choose your platform, install the native CLI, activate Free Preview, and scan a real repository.
1 machine100 filesterminal outputno CI or exports
Verified installer temporarily unavailable
The public release does not yet meet the current license protocol. Install commands will unlock after a compatible signed release is published.
Check release status →Install, activate, and run the first scan.
Activate Free Preview
Claim the machine-bound preview with your email.
radar activate --free --email <your-email>Scan
Run a quick local scan in the current repository.
radar scan . --quickNative release
One workflow across supported platforms.
Use the same activation and scan commands after the platform installer places the signed binary on your path.
macOSApple Silicon and Intel builds
WindowsSigned executable release flow
LinuxNative binary for CI and local shells
Install, activate, and verify the first scan
The download flow installs the native Code Radar CLI on macOS, Windows, or Linux, activates Free Preview for one machine, and verifies the installation with a local scan. The repository remains in the developer workspace or CI runner while the command executes.
- Verify the release source, platform build, binary availability on PATH, CLI version, activation response, and the first terminal finding before adding report exports, MCP, or CI.
- A successful installation proves that the binary runs; it does not prove useful signal on every repository. Proxy policy, file permissions, unsupported platforms, or license connectivity can still require troubleshooting.
- Use the install guide if the binary is unavailable, run a quick scan on real code, compare its evidence with the sample report, and review the security model before sensitive-repository rollout.
How to validate Install, activate, and verify the first scan
Use a real artifact and an explicit boundary for the decision. A claim is useful only when the visitor can inspect it, reproduce the relevant step, and understand what it does not prove.
Decision areaWhat to verify
EvidenceVerify the release source, platform build, binary availability on PATH, CLI version, activation response, and the first terminal finding before adding report exports, MCP, or CI.
BoundaryA successful installation proves that the binary runs; it does not prove useful signal on every repository. Proxy policy, file permissions, unsupported platforms, or license connectivity can still require troubleshooting.
Next stepUse the install guide if the binary is unavailable, run a quick scan on real code, compare its evidence with the sample report, and review the security model before sensitive-repository rollout.
What evidence should I inspect for Install, activate, and verify the first scan?
Inspect this evidence: Verify the release source, platform build, binary availability on PATH, CLI version, activation response, and the first terminal finding before adding report exports, MCP, or CI.
What does Install, activate, and verify the first scan not prove?
Keep this limitation explicit: A successful installation proves that the binary runs; it does not prove useful signal on every repository. Proxy policy, file permissions, unsupported platforms, or license connectivity can still require troubleshooting.
What should I do after reviewing Install, activate, and verify the first scan?
Use the next step that matches the decision: Use the install guide if the binary is unavailable, run a quick scan on real code, compare its evidence with the sample report, and review the security model before sensitive-repository rollout.
Keep source code where the scan runs.
Review the security model before installing Radar on a sensitive repository or adding it to CI.