Weave Code
Style Checker Laravel Package
movingimage/style-checker
A PHP code style checker for Laravel projects from movingimage, helping teams enforce consistent coding standards and catch style violations early so your codebase stays clean, readable, and maintainable.
At a glance
Frequently asked questions about Style Checker
- What is movingimage/style-checker and what does it do?
- movingimage/style-checker is a Composer-installable bundle of configuration for a PHP style tool, most likely PHP-CS-Fixer or PHP_CodeSniffer, intended to enforce a shared coding standard across Laravel projects. It contains no runtime code and is meant to be installed as a require-dev dependency so CI pipelines and developer workstations apply the same formatting rules. Its value proposition is a single shared opinion about code style rather than any new linting engine.
- Is movingimage/style-checker still maintained?
- No. The GitHub repository at MovingImage24/StyleChecker is archived, which means it is read-only and receives no further updates, bug fixes, or security responses. It also has zero stars and zero dependents, so the ruleset has never been validated by an external consumer. Treat abandonment as a realized fact rather than a future risk.
- How do I install movingimage/style-checker in a Laravel project?
- In principle you install it with composer require --dev movingimage/style-checker, since it is dev tooling and should never ship to production. In practice the install is likely to fail because the archived package pins an older php-cs-fixer or squizlabs/php_codesniffer major that conflicts with modern PHP and toolchain versions. If you only want to inspect its rules, clone the repository into a throwaway branch instead of adding it to your real composer.json.
- Does movingimage/style-checker support PHP 8.2 and PHP 8.3?
- Assume it does not until you verify it. An archived package is frozen at the point it was abandoned, and its transitive pin on a specific style-tool major will almost certainly conflict with PHP 8.2 or 8.3 dependencies. Check its composer.json constraints against your oldest supported runtime and current PHP-CS-Fixer major before spending any further time on it.
- What is the difference between movingimage/style-checker and Laravel Pint?
- Laravel Pint is the first-party, actively maintained style tool that already ships as the default in Laravel projects, while movingimage/style-checker is an unmaintained third-party ruleset. Pint tracks PSR-12, the PER Coding Style, and new PHP syntax such as enums and readonly properties, whereas a frozen ruleset will progressively under-format newer language features. For a Laravel codebase, Pint is the framework-aligned choice and competes directly with this package rather than complementing it.
- Should movingimage/style-checker be a dev dependency or a production dependency?
- Always a dev dependency, never production. The package is pure configuration for a style tool, so it belongs in require-dev and its blast radius is limited to CI pipelines and developer machines. Keeping it out of production means it cannot affect request paths, autoloading of application classes, or deployment artifacts.
- Can I reuse the movingimage/style-checker ruleset without depending on the package?
- Yes, and that is the recommended approach if any rule is genuinely valuable. Install it in a throwaway branch or manually clone the repository, dump the resolved ruleset, and diff it against your existing pint.json or .php-cs-fixer.php. Port only the deltas you want into your own config, which then becomes the single source of truth. Lock-in risk is low because the artifact is just text that can be inlined in an afternoon.
- What are the best alternatives to movingimage/style-checker for Laravel code style?
- Laravel Pint is the strongest alternative for Laravel projects because it is first-party, maintained, and already part of the framework's tooling story. For non-Laravel PHP services, a short php-cs-fixer config committed to the repository or a small internal style package delivers the same central-governance benefit with full control. Both options avoid inheriting an unmaintained third party's formatting opinion.
- Why does composer require movingimage/style-checker fail with dependency conflicts?
- The archived package pins a specific php-cs-fixer or PHP_CodeSniffer major from the era it was abandoned, which typically conflicts with modern PHP versions and your current toolchain. Resolving that conflict would mean constraining the rest of your toolchain to match a dead dependency, which is an unacceptable inversion of priorities. Do not fork the package just to unpin it; extract the rules you want into your own configuration instead.
- How do I enforce Laravel code style in CI without adopting an unmaintained package?
- Install Laravel Pint as a dev dependency and run it in dry-run mode in your CI pipeline so violations fail the build. Commit your pint.json to the repository so the standard is versioned and reviewable, and assign an internal owner for style governance. This gives you the cross-repo consistency the abandoned package promised, without the maintenance and security gaps of an archived dependency.
Weaver
How can I help you explore Laravel packages today?