Weave Code
Architecture Laravel Package
phpno1/architecture
A Laravel/PHP package for applying clean architecture principles in real projects. It provides conventions and tooling to organize code into clear layers, reduce coupling, and keep applications consistent, testable, and easier to maintain as they grow. Designed to make architecture decisions explici...
phpno1/architecture brings a clean, layered structure to Laravel applications. It helps you organize code into Domain, Application, Infrastructure, and Presentation layers, keeping business logic independent of framework concerns and making large codebases easier to navigate, extend, and test.
The package provides generators and conventions for each layer, so new features follow a consistent shape. It encourages dependency inversion and separates use cases from controllers, Eloquent models, and external services—ideal when a standard Laravel structure starts to blur boundaries.
- Scaffold layer-based modules with a single command
- Enforce layer boundaries and dependency rules
- Generate use cases, repositories, and DTOs
- Keep domain logic framework-agnostic and unit-testable
- Integrate cleanly with existing Laravel projects
Frequently asked questions about Architecture
- What is phpno1/architecture used for in a Laravel project?
- It presents itself as an architecture package for Laravel, intended to help define clean architecture rules such as layer boundaries, dependency constraints, and automated checks against design drift. In practice it reads more like a reference layered skeleton of controllers, services, repositories, and models to adopt as an internal convention than a bounded library you require in composer.json. That distinction matters when you are deciding whether to install it as a dependency or copy the patterns.
- How do I install phpno1/architecture with Composer?
- A normal composer require is likely to fail at the version gate, because the last release was in April 2018 with constraints aimed at Laravel 5.5 to 5.7 and PHP 7.0 to 7.2. On a modern Laravel 10 or 11 application running PHP 8.x, Composer will refuse the dependency. Practical options are selectively vendoring source files into app/ or forking the package with widened constraints and a PHP 8 compatibility pass.
- Does phpno1/architecture support Laravel 10 or Laravel 11?
- No, not out of the box. The last release predates both by several years, and its composer.json constraints target the Laravel 5.x era and PHP 7.0 to 7.2. Running it on Laravel 10 or 11 requires a fork, widened constraints, and fixes for framework API drift such as container binding signatures, Str and Arr helpers, pagination, and Eloquent return types.
- Which PHP versions does phpno1/architecture require?
- Based on the April 2018 release, expect constraints in the PHP 7.0 to 7.2 range, which conflict with the ^8.1 or ^8.2 floor required by Laravel 10 and 11. You would need to widen those constraints and audit the code for PHP 8 incompatibilities before relying on it.
- Is phpno1/architecture still maintained?
- There have been no maintained releases in more than seven years, and the repository shows a single maintainer, roughly 63 stars, and zero dependents. There is no visible CI signal or security response channel. Treat it as a dormant reference repository rather than a supported dependency.
- Can I use phpno1/architecture in a commercial Laravel project?
- The repository license is reported as NOASSERTION, meaning GitHub could not detect a recognized license file. Without an explicit grant, the legal position on copying source into a commercial codebase is undefined, which is a hard blocker for most enterprises. Resolve licensing in writing with the maintainer before spending engineering time, or reimplement the patterns from the description instead of copying files.
- How does phpno1/architecture compare to Laravel actions, DDD, or repository packages?
- Its concepts, such as thin controllers, a service layer, and repository abstractions over Eloquent, are mainstream and map cleanly onto typical Laravel structure. The difference is that maintained alternatives already exist, including Laravel's own action and pipeline patterns and actively maintained repository or DDD packages. Uniqueness here is near zero, so compare on maintenance, licensing, and PHP 8 support rather than features.
- Does phpno1/architecture include tests, and do they run on modern Laravel?
- There is no CI signal you can read from the repository, and there have been no maintained releases for more than seven years. Even if tests exist in the tree, they would have been written against Laravel 5.x and PHP 7.x, so they will not run unmodified on Laravel 10 or 11. Verify this yourself with a read-only audit before assuming any test coverage.
- How do I migrate an existing Laravel app to the phpno1/architecture structure?
- Treat it as an extraction exercise, not an installation. Start with a read-only audit of composer.json and the class list to separate load-bearing classes from illustrative ones, then settle licensing before copying anything. If licensed, vendor selected files into app/ and adapt them to current framework APIs, or simply reimplement the conventions your team wants.
- What are the production risks of depending on phpno1/architecture?
- The main risks are provenance and licensing under NOASSERTION, abandonment with the last release in April 2018, no security response channel, and a single-maintainer bus factor. Runtime risk is lower because the code is likely small and readable, but that also caps the value, since a senior engineer could write equivalent conventions in an afternoon. The heavier cost is the fork maintenance needed to keep it working on PHP 8 and modern Laravel.
Weaver
How can I help you explore Laravel packages today?