We just released v6.0, a complete rewrite of our open-source linter focused on *keeping web project architectures clean*.

## Problem: Architecture Violations Go Undetected

Most teams don't catch architectural issues until they're expensive: - Circular dependencies (cause cascading changes) - Layer violations (mixing UI with business logic) - Security issues (unsanitized input → DB)

## Solution: Architect Linter v6.0

*Three key improvements:*

1. *CFG-Based Security Analysis (95% accurate)* - Old: Substring matching ("execute" in name = sink) → 80% false positives - New: Control Flow Graph + data flow tracking → <5% false positives - Real vulnerabilities detected. Noise eliminated.

2. *Zero-Config Setup* ```bash architect init # Auto-detects NextJS, Django, Laravel, etc architect lint . # Shows violations ```

3. *Modern Framework Focus* - TypeScript/JavaScript (8 frameworks) - Python (3 frameworks) - PHP (2 frameworks) - Deliberately dropped: Go, Java, C#, Ruby, Kotlin, Rust - (Reason: Web teams use these 3 languages 80% of the time)

## By The Numbers

- 432+ tests (83% coverage) - <5s lint time on typical projects - 0 config needed for common setups - 14 frameworks auto-detected

## For Teams

This solves: "How do I prevent my codebase from becoming unmaintainable?"

Use cases: - Startup CTO: Enforce layer separation as team grows - Enterprise: Security audit of architecture - Open source: Prevent chaos in growing projects

## Status

- v6.0: Production-ready (we use it internally) - v6.1 (planned): Enhanced variable tracking - v7 (roadmap): Pre-commit hooks, CI integration

*MIT Licensed. Written in Rust. Pure CLI (no plugins to slow you down).*

---

What architectural issues are you dealing with in your projects?