ArchLens 0.4.3

Designed for visualizing package dependencies and highlighting differences between branches in GitHub pull requests. It offers customization options to tailor package views.

ArchLens User Guide

ArchLens generates customisable visual internal dependency diagrams of your codebase, showing packages and their dependencies. It currently supports Python, C#, Go, Java & Kotlin. ArchLens also has a dedicted Visual Studio Code extension, you can call it through CLI and can highlight the differences between GitHub branches to make pull request reviews easier.

Table of Contents

• Installation
  • Python projects (PyPi)
  • C# projects and multi-language support
• Configuration
  • Configuration reference
    • Python folder depth constraint
    • C# configuration example
• Commands
• Defining Views
  • Show all top-level packages
  • Expand a specific package
  • Multiple packages in one view
  • Filtering packages
• Diff Views
• VSCode Extension
  • Installation
  • Setup
  • Views in the extension
  • Using the local ArchLens build with the extension
• Multi-Language Support and Better Performance
  • Setup steps

Installation

Python projects (PyPi)

For Python projects, install ArchLens from PyPi:

pip install archlens

Note: Administrative rights may be required. We recommend using a virtual environment.

Python version: Python 3.10 is recommended; Later versions might cause issues.

C# projects and multi-language support

The PyPi package currently supports Python only. For C# projects, or for the latest features and performance improvements, use the local development version. See Multi-Language Support and Better Performance.

Configuration

ArchLens is configured through an archlens.json file in the root of your project. To generate a template, either press ctrl+shift+p and select ArchLens: setup ArchLens, or run:

archlens init

This creates an archlens.json file with the following structure:

{
    "$schema": "https://raw.githubusercontent.com/archlens/ArchLens/master/src/config.schema.json",
    "name": "my-project",
    "rootFolder": "src",
    "github": {
        "url": "https://github.com/owner/my-project",
        "branch": "main"
    },
    "saveLocation": "./diagrams/",
    "views": {
        "completeView": {
            "packages": [],
            "ignorePackages": []
        }
    }
}

Configuration reference

Field	Required	Description
name	Yes	Name of your project
rootFolder	Yes	Path to your source root relative to the project root (e.g. "src")
github.url	For diff commands	URL of the GitHub repository
github.branch	For diff commands	The base branch to compare against (e.g. "main")
fileExtensions	No/Required for non-python projects	File extensions to parse (e.g. [".cs"])
exclusions	No	Folders or files to exclude (e.g. ["obj/", "bin/", "*test*"])
saveLocation	No	Where to save generated diagrams. Defaults to "./diagrams/"
snapshotDir	No	Directory for cache files. Defaults to ".archlens"
snapshotFile	No	Filename for the cache. Defaults to "snapshot"

Python folder depth constraint

For Python projects, rootFolder must have only one level of depth from your project root for dependency arrows to render correctly. For example, use "src" rather than "src/myapp/modules".

C# configuration example

{
    "$schema": "https://raw.githubusercontent.com/archlens/ArchLens/master/src/config.schema.json",
    "name": "MyApp",
    "rootFolder": "src/MyApp",
    "github": {
        "url": "https://github.com/owner/myapp",
        "branch": "main"
    },
    "fileExtensions": [".cs"],
    "exclusions": ["obj/", "bin/", ".vs/", ".git/"],
    "saveLocation": "./diagrams/",
    "views": {
        "completeView": {
            "packages": [],
            "ignorePackages": []
        }
    }
}

Commands

All commands must be run from the root of your project (where archlens.json lives).

Command	Description
archlens init	Creates the archlens.json config template
archlens render	Renders all views defined in the config
archlens render-diff	Renders difference views comparing current branch to the base branch
archlens create-action	Creates a GitHub Actions workflow for automatic PR diff comments

Defining Views

Views control what is shown in each diagram. Each view is a named entry under "views" in your config.

Show all top-level packages

Leave packages empty to show all top-level packages:

"views": {
    "completeView": {
        "packages": [],
        "ignorePackages": []
    }
}

Expand a specific package

Use a path and depth to drill into a package. depth: 1 shows the direct children:

"inside-core": {
    "packages": [
        {
            "path": "core",
            "depth": 1
        }
    ]
}

Multiple packages in one view

"layeredView": {
    "packages": [
        { "path": "Application", "depth": 1 },
        { "path": "Domain", "depth": 2 },
        { "path": "Infra", "depth": 1 }
    ],
    "ignorePackages": []
}

Filtering packages

Use ignorePackages to remove noisy packages from a view. Two filtering modes are supported:

"ignorePackages": [
    "*test*",
    "core/model"
]

• "*test*" — removes any package whose name contains "test"
• "core/model" — removes core/model and all of its sub-packages

Diff Views

Diff views highlight dependency changes between your current branch and the base branch specified in github.branch. Changed elements are shown in green (added) and red (removed).

OBS! to use diff on non-python projects we recommend pushing a cached version (also refered to as the snapshot) to the branch, to optimise performance.

Make sure you are on a feature branch (not the base branch), then run:

archlens render-diff

This generates diagrams only for views that have actual changes. If there are no differences, a diagram without highlights is still generated.

Diff output indicates:

• Green package/arrow — added in the current branch
• Red package/arrow — removed in the current branch
• Count changes on arrows (e.g. 5 (+2))

VSCode Extension

The ArchLens for VSCode extension lets you generate and view architecture diagrams directly inside VS Code.

Installation

Search for ArchLens in the VS Code Extensions panel and install it. You can also install it manually by downloading the .vsix file from the releases page and running:

code --install-extension archlens-<version>.vsix

The extension requires the Python extension for VS Code to be installed.

Setup

1. Open the command palette (Ctrl+Shift+P).
2. Run the ArchLens: Setup command and follow the prompts.

The extension will guide you through creating your archlens.json configuration if one does not exist.

Views in the extension

The extension displays three states:

• Normal view: your current architecture diagram
• Diff view: dependency changes compared to the base branch
• Busy view: while ArchLens is processing

Using the local ArchLens build with the extension

If you are using the local development version of ArchLens (e.g. for C# support), install it into the virtual environment that the extension uses:

pip install -e "<path-to-local-archlens>/src/python"

Multi-Language Support and Better Performance

The PyPi package (archlens) currently supports Python projects only. For multilanguage support and improved performance, you need to use the local build.

.NET version: .NET 9.0 runtime is required to use the multilanguage features

Setup steps

1. Clone the ArchLens repository:

   git clone https://github.com/archlens/ArchLens
   

2. Clone your target project (if not already available locally).

3. In your project, create and activate a virtual environment:

   python -m venv .venv
   # Windows
   .venv\Scripts\activate
   # macOS/Linux
   source .venv/bin/activate
   

   Use Python 3.10 or 3.12. Do not use Python 3.14.

4. Install ArchLens from the local source:

   pip install -e "<path-to-local-archlens>/src/python"
   

5. Build the .NET component:

   dotnet build
   

   dotnet publish "<path-to-archlens>/src/c-sharp/Archlens.csproj" \
       -o "<path-to-archlens>/src/python/src/.dotnet"
   

   This publishes the .NET build output, including the ArchLens DLL, into the .dotnet folder so the Python CLI can invoke it.

6. Run ArchLens in your project:

   archlens init
   archlens render
   

Note: Any time you make changes to the C# source, re-run the dotnet publish command to update the DLL.

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[0.4.3] - 2026-03-21

Fixed

• .NET DLL loading on macOS (and pip installs in general)
• Config files (schema, template) now properly included in PyPI package
• Auto-detect DOTNET_ROOT on macOS Homebrew
• Deduplicated dotnet initialization code into _init_dotnet() helper

[0.4.0] - 2026-03-21

Added

• Multi-language support: C#, Java, Go, and Kotlin (via .NET backend)
• Diff rendering for non-Python projects
• JSON rendering output format
• Comprehensive C# test suite (~3,400 lines)
• CONTRIBUTING.md with development setup instructions

Changed

• pythonnet used to bridge Python CLI with .NET parsers
• .NET DLLs no longer committed to repo; built via dotnet publish before packaging
• fileExtensions config field determines which parser to use

[0.3.0] - 2025-11-27

Changed

• render_diff_views now only generates images for views with actual architectural changes
• CLI outputs ARCHLENS_CHANGED_VIEWS=<view1>,<view2>,... to indicate which views have changes

[0.2.9] - 2025-06-23

Bugfix

• Default view shows top level packages not all the packages in the system

[0.2.8] - 2025-06-23

Bugfix

• Fixed package depth functionality that was not working properly: when depth is 2 the view should not show nodes at depth 1 or 3! (with Sebastian Cloos Hylander)