Product
Archito NewLearns from your merge requests and flags what is stuck Integrations 25
Solutions
By role
Why AppArch
Resources
Customers Pricing Contact
Language
Contact us

One measurable quality score for your whole codebase.

ArchScan scans the whole codebase and reports SOLID violations, dependency issues and architectural smells with a category-weighted score.

Screens from a running installation

Anatomy of a report

Every scan produces a full, seven-section report.

Summary score

One weighted score + status.

Findings

With code snippet and file location.

SOLID

Violation breakdown per principle.

Packages

Dependencies and versions.

Projects

Per-project metrics.

Dependency map

Interactive graph view.

From repository to score

A full scan reads the whole codebase in your CI; the panel turns what it finds into a score you can compare release to release.

  1. The whole repository

    On a schedule, on demand or alongside the MR pipeline, in nine languages.

  2. Analyser in your CI

    Rules come from the panel; the repository is never uploaded.

  3. What comes back

    Findings with code snippets, packages and versions, per-project metrics, line counts.

  4. Scored in the panel

    Severity-weighted findings per 1,000 lines, then duplication and complexity.

  5. Report and map

    The seven-section report, the dependency map and an HTML/PDF export.

How the score is calculated

The same formula for every project, so a small service and a large monolith are judged fairly.

  1. Each finding is weighted by its severity.

  2. The weights are counted per 1,000 lines of code; as that density rises, the score falls exponentially.

  3. Then deductions: duplication above 3% costs up to 15 points, methods with complexity above 20 up to 10.

  4. Ceilings: one critical finding caps the score at 79; five critical findings, or one error per 1,000 lines, cap it at 69.

See your architecture, don't just read it

Cross-project dependencies come alive in an interactive graph - spot cycles and leaks at a glance. Export the report as shareable HTML/PDF.

Intended
In the code
  • Allowed dependency
  • Layer breach: the domain depends on infrastructure
  • Cycle: application and infrastructure depend on each other

First the layering you intended, then what the code really does. ArchScan's map draws the second picture from the code itself.

What's inside the report

Every scan turns into a concrete scorecard your team can act on.

01

Category-weighted score

Architecture, SOLID, dependency and metric categories collapse into one weighted score that's comparable across releases.

02

Findings with code snippets

Each finding ships with the relevant code snippet and exact file location - no guessing, jump straight to the line.

03

SOLID breakdown per principle

Violations are split across the five SOLID principles, so you see exactly where you struggle most.

04

Package & project metrics

Dependencies, versions and per-project metrics are gathered in one report.

05

Interactive dependency map

Cross-project dependencies are explorable in an interactive graph - spot cycles and layer leaks at a glance.

06

Shareable export

Export the report as HTML/PDF, with the report language set per workspace. The scan runs in your own CI.

See it in the product

All screenshots

Get your first report in minutes

Connect, scan, see your score - scans run on your own infrastructure.

Join our newsletter

New modules, release notes and writing on architecture. Leave with one click whenever you like.