Download the PHP package cooldevguys/phpstan-dhexpendency-rules without Composer
On this page you can find all versions of the php package cooldevguys/phpstan-dhexpendency-rules. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download cooldevguys/phpstan-dhexpendency-rules
More information about cooldevguys/phpstan-dhexpendency-rules
Files in cooldevguys/phpstan-dhexpendency-rules
Package phpstan-dhexpendency-rules
Short Description A set of rules for PHPStan based on the Hexagonal architecture layers dependency
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package phpstan-dhexpendency-rules
🧭 phpstan-dhexpendency-rules
A set of additional PHPStan rules that help enforce the
dependency flow of a hexagonal (ports & adapters) architecture — so a stray use statement in
the wrong direction gets caught in CI, not in code review. 🚦
📐 The rule this package enforces
These rules assume the typical hexagonal architecture with 3 layers: Infrastructure, Application and Domain, and that dependencies must only ever flow one way:
In other words:
| Layer | May depend on | May not depend on |
|---|---|---|
| 🏗️ Infrastructure | Application, Domain, external vendors | (nothing forbidden) |
| ⚙️ Application | Domain only | Infrastructure |
| 🧠 Domain | itself only | Infrastructure, Application |
The Domain layer is the one that matters most to protect: it's your business logic, and it should never know that a database, an HTTP client, or a specific framework exists.
✨ What you get
LayersDependencyFlowRule— flags anyusestatement that points from a layer to a layer it isn't allowed to depend on (per the table above).NoExternalVendorsAllowedRule(opt-in viavendorStrictMode) — flags anyusestatement in the Application or Domain layers that imports a class from outside your own project vendor namespace (e.g. a third-party library), so your business logic only talks to your own code — never directly to a framework or SDK. Infrastructure is always exempt, since it's exactly the layer meant to talk to the outside world.
📦 Installation
⚠️ Dev-only package. This is a static analysis tool — its rules only run while
phpstan analyseruns, never in your application's runtime code. Always install it with--dev(as below) so it lands inrequire-dev, notrequire, and never ships to production. If you forget the flag, Composer itself will notice (this package is taggedstatic analysis) and offer to re-run the command with--devfor you.
If you use PHPStan's extension installer,
you're all set. 🎉 Otherwise, register the rules manually in your phpstan.neon:
Requirements: PHP >=7.4 and phpstan/phpstan ^2.0.
⚙️ Configuration
Add your project's values nested under a single dhexpendency key in phpstan.neon:
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
myVendorName |
string |
✅ | — | Your project's top-level namespace segment (e.g. CoolDevGuys in CoolDevGuys\App\...). Must be a valid PHP identifier. |
infrastructureLayerName |
string |
✅ | — | The namespace segment you use for the Infrastructure layer. |
applicationLayerName |
string |
✅ | — | The namespace segment you use for the Application layer. |
domainLayerName |
string |
✅ | — | The namespace segment you use for the Domain layer. |
vendorStrictMode |
bool |
❌ | false |
Enables NoExternalVendorsAllowedRule (see above). |
ignoredExternalVendors |
string[] |
❌ | [] |
Vendor namespaces exempted from vendorStrictMode. Only has an effect when vendorStrictMode is true. |
The three layer names must all be different from each other, and every name above must be a valid PHP namespace segment (letters, digits, underscores; can't start with a digit) — an invalid value fails fast with a clear error instead of silently misbehaving.
⬆️ Upgrading from 1.x?
This is a breaking change (v2.0): parameters moved from the top level of
parameters:into a nesteddhexpendency:key, andNoExternalVendorsAllowedFromDomainRulewas renamed toNoExternalVendorsAllowedRule(it always checked Application and Domain, not just Domain — the new name matches what it actually does). To migrate, just move your existing six keys underdhexpendency:as shown above; nothing else changes, and no error messages or rule identifiers were affected, so anyphpstan-baseline.neonyou already generated stays valid.
🧩 How your namespaces should look
Each layer is identified by a segment in the namespace, placed after your vendor name and an optional "context" segment — for example, with the config above:
When a namespace could plausibly match more than one configured layer name at different depths, the leftmost (earliest, shallowest) match wins — so a Domain module with an unrelated nested segment that happens to share a name with another layer is still correctly recognized as Domain. Files whose namespace doesn't start with your configured vendor name, or has no recognizable layer segment at all, are silently skipped by both rules (they're none of this package's business).
🚨 What a violation looks like
Both errors carry a stable 🪪 identifier, so
if you ever need to allow a specific case, you can target it precisely in phpstan.neon:
🧭 Scope & limitations
This package covers the classic 3-layer hexagonal setup with a single project vendor namespace. It does not support additional layers (e.g. a separate Presentation/UI layer) or checking more than one vendor namespace at once.
🧪 Development
Pull requests are welcome! Please make sure vendor/bin/phpunit passes before opening one.
📄 License
MIT © Alejandro Romero — see LICENSE.md.
