Coke Laravel Package

Product Decisions This Supports

• Legacy Codebase Maintenance: If your team is maintaining an older Laravel/PHP codebase that relies on strict coding standards (e.g., PSR-12, custom rules), this package could simplify configuration of PHP Code Sniffer (PHPCS)—though it’s deprecated, it may still be embedded in legacy workflows.
• Build vs. Buy: Avoid reinventing a wheel for PHPCS configuration if your team lacks the bandwidth to build a custom solution. This package was a lightweight alternative to manual setup.
• Compliance & Onboarding: Useful for enforcing consistent coding standards during developer onboarding or pre-commit hooks (if still integrated into CI/CD pipelines).
• Deprecation Migration: If your team is transitioning from this package, it could serve as a reference for understanding how to migrate to modern alternatives (e.g., php-cs-fixer or custom PHPCS rulesets).

When to Consider This Package

• Only if:
  • Your project actively uses this package in its current state (e.g., it’s hardcoded in composer.json or CI scripts).
  • You’re maintaining a legacy Laravel/PHP codebase where this package was previously adopted and no migration has occurred.
  • Your team lacks resources to replace it with a modern alternative (e.g., php-cs-fixer or native PHPCS configuration).
• Look elsewhere if:
  • You’re starting a new project or modernizing an existing one (this package is archived since 2017 and unsupported).
  • You need active maintenance, security updates, or new features (use php-cs-fixer or custom PHPCS rulesets instead).
  • Your team prioritizes long-term sustainability over short-term convenience.

How to Pitch It (Stakeholders)

For Executives: "This package was a lightweight tool to automate PHP Code Sniffer configuration in Laravel projects, reducing manual setup time for coding standards. However, it’s deprecated and no longer maintained. If we’re still using it, we should assess the effort to migrate to a modern alternative (e.g., php-cs-fixer) to avoid technical debt. The risk of using unsupported software outweighs the minimal benefit for new or greenfield projects."

For Engineering Teams: *"The m6web/coke package simplified PHPCS setup in older Laravel apps, but it’s archived and unsupported. If we’re relying on it:

1. Audit its usage—is it critical to CI/CD or developer workflows?
2. Plan a migration to php-cs-fixer or native PHPCS rulesets (lower maintenance, actively developed).
3. Deprecate it in favor of modern tools to future-proof our codebase. For new projects, avoid this package entirely—it’s a legacy solution with no path forward."*