Phpstan Symfony Laravel Package

Product Decisions This Supports

• Legacy System Modernization: If maintaining an older Symfony 2/3 application and evaluating static analysis tools, this package could be a low-cost option to integrate PHPStan (a modern static analyzer) into legacy workflows without full framework upgrades.
• Cost Optimization: For teams with tight budgets, leveraging a deprecated but functional package may reduce licensing costs associated with newer alternatives (e.g., paid PHPStan extensions).
• Technical Debt Reduction: If the team is already using PHPStan and needs Symfony-specific rule enforcement, this package could bridge gaps until a modern replacement is developed or adopted.
• Proof of Concept (PoC): Useful for experimenting with static analysis in Symfony projects before committing to a more robust solution (e.g., custom PHPStan rules or newer Symfony-compatible extensions).

When to Consider This Package

• Avoid if:
  • Using Symfony 4+ or modern PHPStan (v1.0+)—this package is incompatible and deprecated.
  • Seeking active maintenance or security updates—last release was 2018; no support for modern Symfony/PHPStan features (e.g., dependency injection, attributes).
  • Requiring enterprise-grade reliability—risk of breaking changes with newer Symfony/PHPStan versions.
  • Preferring built-in or officially supported solutions (e.g., PHPStan’s native Symfony support in later versions).
• Consider if:
  • Working on a niche, long-term-maintained Symfony 2/3 codebase with no plans for upgrades.
  • Evaluating low-risk static analysis for small teams or open-source projects where cost is a priority over cutting-edge features.

How to Pitch It (Stakeholders)

For Executives: "This deprecated package offers a lightweight way to integrate static code analysis into legacy Symfony 2/3 applications at minimal cost. While not ideal for new projects, it could help us identify technical debt in older systems without major rework. However, we should pair this with a plan to migrate to a supported solution (e.g., custom PHPStan rules or newer extensions) within [X] months to avoid long-term risks."

For Engineering: *"The lookyman/phpstan-symfony package provides basic Symfony rule checks for PHPStan, but it’s outdated and incompatible with modern setups. If we’re stuck on Symfony 2/3 and need some static analysis, we could use it as a temporary stopgap—though we’d need to:

1. Test thoroughly (expect edge cases with newer PHPStan versions).
2. Document limitations (e.g., no support for Symfony 4+ features like attributes).
3. Plan a migration to PHPStan’s native Symfony support or a maintained alternative. For new projects, this isn’t viable; we should explore [alternative X] instead."*