Cordon ModulithCordon off your modules

Verifiable boundaries between the modules of a Laravel application, checked in CI.

Public API per module

Other modules may only use a module's contracts, events, data objects, enums and exceptions, or classes you mark with

Works with your layout

nwidart/laravel-modules, InterNACHI/modular or a plain app/Modules folder, detected automatically. Nothing to scaffold.

Static, never runs your code

Parses files with nikic/php-parser. Works on code that doesn't boot and classes that don't exist yet. Around a second for 1,000 files on a CI runner.

Adopt gradually

Record existing violations in a baseline and fail the build only on new ones.

Where you already work

GitHub annotations, a Pest expectation, a PHPStan rule for your editor and a Laravel Boost skill for AI agents.

Living documentation

Mermaid diagrams, a canvas per module and an event inventory, generated from the code.

text

$ php artisan cordon:verify

Cordon analysed 212 files in 6 modules (148 cross-module references).

x [internal_access] Modules/Billing/app/Services/CheckoutService.php:13
  Module [Billing] uses Modules\Catalog\Models\Product, which is internal to module [Catalog]. Depend on its public API instead (a class in a public namespace such as Contracts, or one marked #[PublicApi]).

x [cycles]
  Modules [Billing, Catalog] form a dependency cycle: Billing -> Catalog -> Billing. Break it by inverting one dependency, for example with an event or a contract.

2 boundary violations.