Download the PHP package odinns/coding-style without Composer

Odinns Coding Style

Shared Rector and PHPStan defaults for Laravel projects.

This package gives Laravel apps a small, boring way to share static-analysis and automated-refactoring rules. The package owns the defaults. Each application owns its paths, baselines, ignore rules, and local skips.

That split matters. Shared config should describe current taste. Local config should describe local history.

Requirements

• PHP ^8.3
• Composer 2
• Rector 2
• PHPStan 2
• Laravel 11, 12, or 13 through Larastan support

Installation

Install the published package as a development dependency:

The package installs Rector, PHPStan, Larastan, and the supported PHPStan extensions it configures.

Local Path Install

For local development, install this checkout into another Laravel project as a Composer path repository:

Then copy the starter config files:

If the consuming project already has rector.php or phpstan.neon, merge the package calls into the existing files instead of overwriting them.

Rector

Create a rector.php file in the consuming project:

Then add Composer scripts:

Run Rector in check mode:

Apply changes:

Local Rector skips

Keep skips in the consuming project:

Do not upstream local skip lists into this package. A skip caused by one app's history is not a coding standard.

PHPStan and Larastan

Create a phpstan.neon file in the consuming project:

Then add Composer scripts:

Run PHPStan:

Baselines

Baselines belong to the consuming project:

Generate a baseline:

Baselines are debt registers. Keep them local and shrink them when the code changes nearby.

Local ignores

Project-specific ignores also stay local:

If an ignore only makes sense in one app, it does not belong in this package.

Included Defaults

Rector

The shared Rector setup enables conservative automated improvements:

• dead-code cleanup
• code-quality cleanup
• type declaration improvements
• safe privatization
• early returns
• import cleanup
• required declare(strict_types=1); declarations
• PHP 8.3 set support
• Laravel relation generic return types
• Laravel model casts method migration
• Laravel validation rule array conversion

The package automatically uses the consuming project's phpstan.neon when it exists, falling back to phpstan.neon.dist. It also loads Larastan's bootstrap file when the consuming project has one installed.

PHPStan

The base PHPStan config enables:

• deprecation rules
• Mockery support
• stricter return type checks
• missing override attribute checks
• safer array-offset reporting
• less overconfident PHPDoc treatment

The Larastan config adds:

• Larastan
• model property checks
• Octane compatibility checks

Stubs

Copy-ready stubs are included:

They are deliberately plain files. No generator command. No plugin. No theatrical machinery.

Update Strategy

Use normal Composer updates:

After updating, run:

If Rector proposes a large change set, review it as a normal refactor. Automated does not mean harmless. It means repeatable.

Design Principles

• Shared defaults should be stable and boring.
• Local paths stay local.
• Local skips stay local.
• Local baselines stay local.
• Rules should remove noise, not rewrite taste every Tuesday.
• The package should be easy to delete from a project if it stops earning its keep.

What This Package Does Not Do

• It does not publish Laravel config.
• It does not register a service provider.
• It does not add migrations, routes, views, or commands.
• It does not own application-specific baselines.
• It does not own application-specific Rector skips.
• It does not try to format code. Use a formatter separately.

Testing With Pest

The package test suite uses Pest.

Add tests under tests/Unit:

Run the suite:

Developing This Package

Install dependencies:

Run all checks:

Run checks separately:

Contributing

Keep changes small and explain the behavior change. Add shared rules only when they are broadly useful across Laravel projects.

Do not add one application's skip list, baseline, or legacy exception to this package. That path leads to a swamp with invoices.

Security

If you discover a security issue, report it privately to the maintainer instead of opening a public issue.

License

The MIT License. See LICENSE.