Psr2R Sniffer Laravel Package

Technical Evaluation

Architecture fit is strong for Laravel projects using PHP_CodeSniffer directly (not Laravel Pint), as it extends PHP_CodeSniffer with PSR-2-R standards. However, conflicts arise with Laravel's default Pint (PHP CS Fixer-based) tooling, creating a fundamental toolchain mismatch. The package requires PHP 8.1+ which aligns with modern Laravel versions.

Integration feasibility is moderate: Composer installation is straightforward, but phpcs.xml configuration requires careful sniff selection. CI integration (GitHub Actions, etc.) is well-documented, though Blade template handling is unsupported out-of-the-box – requiring explicit exclusions or custom rules.

Technical risks include:

• Low adoption (0 dependents, 32 stars) indicating limited real-world validation
• PSR-2-R is non-standard (rectified variant of PSR-2), creating potential compatibility gaps with existing codebases or third-party libraries
• Blade template handling is unaddressed in documentation, risking false positives or missed issues in Laravel-specific files
• Future release uncertainty (last release date shows 2026-01-24 – likely a typo, but indicates unstable release cadence)

Key questions:

• How does this handle Laravel's Blade syntax