MAGDOX Code Security documentation
Overview
What MAGDOX Code Security is, its three components, and how a scan becomes a finding in your dashboard.
Status: Preview
MAGDOX Code Security scans locally and reports centrally. The magdox CLI runs on a developer machine or CI runner and analyses the repository in place, so source code never leaves your environment. Only the results, a structured findings payload, are sent to your organisation's dashboard, where security teams track every repository, triage findings and produce reports.
The three components
| Component | Runs where | Responsibility |
|---|---|---|
| magdox CLI | Developer machine or CI runner (Windows, macOS, Linux) | Authenticates, pulls signed rules and vulnerability data, scans locally, builds the local report, uploads the findings payload, downloads reports. |
| Rules and data service | MAGDOX cloud | Serves signed, versioned rule bundles and vulnerability database snapshots to authenticated CLIs. |
| Dashboard | MAGDOX cloud, or self-hosted by arrangement | Receives findings payloads; tracks findings across runs and repositories; triage, decisions, baselines, reports, exports, organisation and access administration. |
A scan in one paragraph
Sign in once with magdox login. In a repository, run magdox scan. The CLI checks it has current signed rules, scans the working tree on the local machine, writes a local report, and uploads the findings payload. Open the run in the dashboard to triage, or pull the report and exports with magdox report and magdox export. Reviewer decisions made in the dashboard are matched to findings by fingerprint and carried into every later scan.
What leaves your environment
- Findings metadata: rule identifier, file path, line range, fingerprint hash, severity, confidence, message.
- Software inventory components (names, versions, licences) for SBOM and dependency tracking.
- Run metadata: repository identifier, commit hash, branch, CLI and rule versions, timing, coverage counts.
- Code snippets only if your organisation opts in (off by default).
These pages are preview documentation used to design the product. Commands, flags, screens and field names are placeholders finalised with each release. Access is arranged with our team: use the contact form or book a call.