Deply is a static code analysis tool for Python that helps you communicate, visualize and enforce architectural decisions in your projects. You can freely define your architectural layers over classes and which rules should apply to them.
For example, you can use Deply to ensure that modules/packages in your project are truly independent of each other to make them easier to reuse.
Deply can be used in a CI pipeline to make sure a pull request does not violate any of the architectural rules you defined. With the optional Mermaid formatter you can visualize your layers, rules and violations.
You can find the documentation in the /doc directory or visit the doc page: https://vashkatsi.github.io/deply
You can install Deply via pip:
pip install deplyOnce you have installed Deply, you will need to create a configuration file, where you define your layers and communication ruleset. This configuration file is written in YAML and, by default, is stored with the name deply.yaml in your project's root directory.
When you have this file, you can analyse your code by running the analyze command:
deply analyze
# which is equivalent to
deply analyze --config=deply.yamlIn order to run Deply you need at least Python 3.8. Supported and tested versions: Python 3.8 to 3.14.
Here's a simple example of a deply.yaml configuration file:
deply:
paths:
- /path/to/your/project
exclude_files:
- ".*\\.venv/.*"
layers:
- name: models
collectors:
- type: class_inherits
base_class: "django.db.models.Model"
- name: views
collectors:
- type: file_regex
regex: ".*/views_api.py"
- name: services
collectors:
- type: class_name_regex
class_name_regex: ".*Service$"
ruleset:
views:
disallow_layer_dependencies:
- models
services:
disallow_external_imports:
- django
- requestsCode elements may belong to multiple layers. Deply checks every unique source and target layer pair, so layer and collector order does not change dependency or external-import results.
# Basic usage
deply analyze
# With a specific config file
deply analyze --config=custom_config.yaml
# Validate configuration only
deply validate --config=custom_config.yaml
# Generate a Mermaid diagram
deply analyze --mermaid
# Get help
deply --helpdeply analyze validates the configuration before scanning project files and
exits with status 1 when the configuration is invalid or analysis is
incomplete because files cannot be read or parsed, no Python files are found,
or no code elements map to configured layers.
Deply v1.0.0 includes a portable Agent Skill at skills/deply-config/ for Codex, Claude Code, and other Agent Skills-compatible assistants. It helps an assistant inspect a Python project, generate deply.yaml with light, medium, or strict architecture rules, validate it with deply validate, run analysis, and add Makefile/CI/docs integration.
Use it with:
Use $deply-config to create and validate a Deply architecture config for this Python project.
See Agent Skill for installation instructions.
- Layer-Based Analysis: Define project layers and restrict their dependencies to enforce modularity.
- Dynamic Layer Configuration: Easily configure collectors for each layer using file patterns, class inheritance, and logical conditions.
- Cross-Layer Dependency Rules: Specify rules to disallow certain layers from accessing others.
- External Import Restrictions: Prevent selected layers from importing framework, persistence, or SDK packages.
- Extensible and Configurable: Customize layers and rules for any Python project setup.
- Mermaid Diagrams: Visualize your architecture and dependencies with Mermaid diagrams.
- Error Suppression: Suppress specific rule violations with inline comments.
- Config Validation: Validate
deply.yamlexplicitly or automatically before analysis. - Architecture Recipes: Start from validated configurations for 21 architecture and application patterns.
Deply provides options to suppress rule violations using comments in your code:
# Line-level suppression
user.get() # deply:ignore:DISALLOW_LAYER_DEPENDENCIES
import requests # deply:ignore:DISALLOWED_EXTERNAL_IMPORT
# File-level suppression (at the top of the file)
# deply:ignore-file:ENFORCE_INHERITANCEFeel free to contribute to this project by opening an issue or submitting a pull request! Together, we can make Deply a powerful tool for the Python community.
Use the following commands for local quality checks:
make check
make test
make mutation
make lint
make typing
make security
make pre-commitOr run unittest directly:
python -m unittest discover testsA plan to evolve Deply into a must-have architectural guardian for Python projects:
🔲 Skip violations skip_violations
🔲 Interactive config setup (deply init wizard)
🔲 GitHub Actions/GitLab CI templates
✅ # deply:ignore suppression comments
✅ Config validation command (deply validate)
✅ Parallel file analysis
✅ Custom collectors system
🔲 Dependency graph caching
🔲 Custom rules system
✅ FastAPI/Django/Flask configuration recipes
✅ Architecture and application pattern recipes
✅ LLM skill creation helpers
✅ Third-party import restrictions (disallow_external_imports)
See the verified technical roadmap for priorities, evidence, and implementation conditions.
- Core Concepts - Explains layers, rules and violations in more details.
- Configuration - Reference for all available settings in a depfile
- Collectors - Reference for which collectors are available in Deply to define your layers.
- Rules - Lists the different rule types supported by Deply
- Mermaid Diagrams - Overview of the diagram generation capabilities
- Command Line Interface - Advice for using the CLI
- Agent Skill - Install and use the Deply Config Agent Skill
- Architecture Styles - Compare 21 architecture and application pattern recipes
- FastAPI - Configure layered FastAPI boundaries
- Full Stack FastAPI Template - Verified baseline for FastAPI's official template
- Django - Configure Django model, view, and domain boundaries
- Flask - Configure Flask route, blueprint, and persistence boundaries
See the LICENSE file for details.