What Is ScanDrix And How Does It Work?

ScanDrix is an autonomous AI-powered code review and AST security scanning platform built for modern engineering teams. It integrates into your Git providers (GitHub, GitLab, Bitbucket, Azure Repos) to automatically review pull requests, detect vulnerabilities, suggest code fixes, and enforce custom Drixy rules.

How Does ScanDrix Differ From Traditional Linters Like SonarQube?

Traditional linters analyze files in isolation using rigid regex or pattern rules, resulting in high false-positive rates and zero understanding of code intent. ScanDrix performs deep Abstract Syntax Tree (AST) analysis combined with multi-model AI reasoning, understanding whole-codebase context, taint flows, and architectural boundaries.

What Are Drixy Rules And How Do I Configure Them?

Drixy rules are customizable code review and security policies. You can define rules globally across your organization, per repository, or choose from a library of community best practices. You can also run 'Dry Run' previews to test rule modifications against real historical PRs before enforcing them.

Which Git Providers And CI/CD Tools Does ScanDrix Support?

ScanDrix supports GitHub, GitLab, Bitbucket, Azure Repos, and Forgejo out of the box. It also provides a CLI and team API keys for local developer workflows, pre-commit hooks, and custom CI/CD runners.

Does ScanDrix Train On Our Private Source Code?

No. ScanDrix never uses customer source code to train AI models. All code diffs are processed in ephemeral, isolated environments with strict zero-data-retention guarantees. For enterprise deployments, ScanDrix supports Bring Your Own Key (BYOK) and self-hosted on-premise installations.

How Fast Are ScanDrix Code Reviews On New Pull Requests?

ScanDrix is built for sub-minute reviews: an async worker architecture picks up webhook events without blocking CI pipelines. That is a design goal, not a measured guarantee — live service state is on the status page.

Can ScanDrix Suggest Inline Code Fixes?

Yes. When ScanDrix detects bugs, security vulnerabilities, or rule violations, it generates precise inline diff suggestions directly in the pull request review comments that developers can apply with a single click.

Can We Deploy ScanDrix On-Premise Or In Our Own VPC?

Yes. Enterprise customers can deploy ScanDrix in their own AWS, GCP, or Azure VPC, or in fully air-gapped on-premise environments with support for internal LLM endpoints (vLLM, Ollama) and enterprise SSO.

scandrix.yml Reference

Configure active rules, path filters, and severities per repository with scandrix.yml.

Place a scandrix.yml or .scandrix.yml file at the repository root to configure ScanDrix behavior for that repository. Changes take effect on the next pull request — no dashboard action needed.

Full example

yaml

version: 1
project: "my-service"
rules:
  - rule: "enforce-parameterized-sql"
    severity: "critical"
  - rule: "tenant-isolation-guard"
    severity: "critical"
  - rule: "no-hardcoded-secrets"
    severity: "critical"
ignore_paths:
  - "vendor/**"
  - "dist/**"
  - "**/*.spec.ts"

Fields

`version`

Schema version. Currently 1.

`project`

Optional label for the repository. Appears in review summaries and Cockpit-style metrics so monorepo services stay distinguishable.

`rules`

Explicit list of rules to activate for this repository. Each entry may override severity. Rules inherited from the organization scope are active even if not listed — add them here only to change severity.

yaml

rules:
  - rule: "unbounded-goroutine-spawn"
    severity: "warning"   # downgrade from critical
  - rule: "legacy-regex-style"
    severity: "info"      # keep, but never block

`ignore_paths`

Glob patterns excluded from analysis. Excluded files are never parsed, never sent to a model, and never commented on.

Ignore paths are also respected by the security engine — excluding a directory means ScanDrix cannot flag issues there. Exclude generated code, vendored dependencies, and fixtures, not source directories you own.

Precedence

Configuration resolves in this order (later wins):

Organization defaults (dashboard)
Repository settings (dashboard)
scandrix.yml in the repository root
Per-PR overrides via bot comment commands

The effective configuration is shown in the dashboard under Repositories → Settings → Effective Config, including which file each value came from.

Validation

CI validates the file on push:

bash

scandrix config validate

An invalid file fails the check with a line-anchored error; reviews continue with the last known-good configuration so a typo never blocks your pipeline.

PreviousConfiguration File (.scandrix.yaml)NextDry Run Testing