- What is ongr/ongr-strict-standard?
- ONGR Strict Standard is a PHP_CodeSniffer ruleset that enforces strict coding conventions based on PSR-2 and Squiz standards. It is a development-time linting tool, not a Laravel runtime package, so it does not affect routing, persistence, or application behavior. Teams would use it in CI or local tooling to catch style and quality issues early.
- Is ongr/ongr-strict-standard still maintained?
- No. The package is archived, has no active maintainer, and was last released in 2015. It has very low adoption and no upstream support for modern PHP or PHPCS versions. Treat it as a reference implementation rather than a default dependency.
- How do I install ongr/ongr-strict-standard in a Laravel project?
- In principle you would add it as a require-dev Composer dependency and reference its ruleset from a project-owned phpcs.xml file. However, the archived Composer constraints may conflict with current Laravel, PHP, and PHPCS versions. Run a short compatibility spike before adding it to any real workflow.
- Does ongr/ongr-strict-standard support Laravel?
- It is a framework-agnostic PHP_CodeSniffer ruleset, so it has no Laravel-specific integration or awareness of Laravel conventions. It could technically run in a Laravel CI job, but modern Laravel projects typically use Laravel Pint and PSR-12 instead. Adoption is not recommended unless you have a specific unmet strictness requirement.
- Which PHP and PHPCS versions does ongr/ongr-strict-standard support?
- The available context does not document current version support, and the package was last released in 2015. That strongly suggests old PHPCS constraints and likely incompatibility with modern PHP 8.x and PHPCS 3.x or 4.x. You must prove Composer resolution and sniff compatibility before relying on it.
- Can I use ongr/ongr-strict-standard together with Laravel Pint?
- There is no direct integration because Laravel Pint is built on PHP-CS-Fixer, while this package is a PHP_CodeSniffer ruleset. You could run both as separate tools, but that adds redundant and potentially conflicting style enforcement. For most Laravel teams, Pint alone or PHPCS with PSR-12 is the cleaner choice.
- What is the difference between ongr/ongr-strict-standard and PSR-12?
- This package is based on the older PSR-2 standard plus Squiz strictness rules, while PSR-12 is the current coding style specification that superseded PSR-2. The package may include stricter legacy checks, but it lacks modern PHP syntax awareness. Review whether those specific sniffs justify the maintenance burden.
- Should ongr/ongr-strict-standard be used in production?
- No. It is development-time linting tooling and should only ever be a require-dev dependency used in local or CI environments. It has no runtime role and should not be deployed to production. Keeping it out of production also limits supply-chain and reliability exposure.
- Can I fork ongr/ongr-strict-standard if I need it?
- The MIT license permits forking, but forking creates real internal ownership for PHPCS updates, PHP version support, and sniff fixes. Because this is a dev-only ruleset, the engineering cost may outweigh the benefit. Only fork if you have a specific strictness requirement that Pint or a maintained PSR-12 ruleset cannot satisfy.
- What are the best alternatives to ongr/ongr-strict-standard for Laravel?
- Laravel Pint and PHP_CodeSniffer with a maintained PSR-12 ruleset are the standard choices for modern Laravel projects. Pint is the default Laravel style tool and requires little configuration, while PHPCS with PSR-12 gives more granular CI enforcement. Prefer these maintained options unless you specifically need legacy Squiz-based strict sniffs.