Phpstan Generic Rules Laravel Package

Product Decisions This Supports

• Developer Productivity & Code Quality: Enables stricter static analysis for PHP/Laravel projects, reducing runtime errors and improving maintainability. Aligns with initiatives to automate quality checks in CI/CD pipelines.
• Technical Debt Reduction: Helps enforce consistent coding standards and catch edge cases early, supporting long-term maintainability of legacy or rapidly growing codebases.
• Scalability & Reliability: By catching type-related issues (e.g., generics, null safety) before deployment, reduces production incidents, which is critical for high-traffic Laravel applications.
• Build vs. Buy: Avoids reinventing custom static analysis tools; leverages an open-source, community-vetted solution to augment existing PHPStan rules.
• Roadmap Prioritization: Justifies investment in tooling for teams adopting modern PHP features (e.g., generics, attributes) or migrating to Laravel 10+.

When to Consider This Package

• Adopt if:

  • Your team uses PHPStan for static analysis and wants to extend its capabilities with generic type rules (e.g., validating collections, arrays, or custom generics).
  • You’re maintaining a large Laravel codebase with complex type hierarchies (e.g., repositories, services, or DTOs) where runtime type errors are costly.
  • You prioritize preventative quality over reactive debugging, especially in CI pipelines.
  • Your team is already familiar with PHPStan and needs fine-grained control over rule customization.

• Look elsewhere if:

  • You’re not using PHPStan (this is a plugin, not a standalone tool).
  • Your project is small or prototype-scale with minimal type complexity.
  • You lack developer bandwidth to integrate and maintain custom static analysis rules.
  • Your primary pain points are performance (this adds analysis overhead) or runtime behavior (not static analysis).

How to Pitch It (Stakeholders)

For Executives: "This package supercharges our PHP/Laravel code quality by adding advanced static analysis rules to PHPStan—catching type-related bugs early, reducing production incidents, and cutting debugging time. For a minimal investment (open-source, low maintenance), it aligns with our goals of scalability and reliability. Teams using Laravel 10+ or complex generics will see the biggest ROI."

For Engineering/DevOps: *"PHPStan already gives us static analysis, but korbeil/phpstan-generic-rules fills gaps in generic type safety—think stricter validation for collections, repositories, or custom DTOs. It’s a drop-in extension that:

• Reduces runtime errors by enforcing type constraints at dev time.
• Integrates seamlessly with existing PHPStan configs (no major setup).
• Works in CI to block flawed PRs before merge. Best for teams already using PHPStan; if you’re not, this is a great reason to adopt it."*

For Developers: *"If you’ve ever fought with PHPStan’s default rules missing edge cases (e.g., generics, null in collections), this package adds 10+ custom rules to tighten your analysis. Example use cases:

• Validate that a Collection always contains User models, not mixed types.
• Enforce null safety in repository methods.
• Catch inconsistent return types in services. It’s like upgrading PHPStan’s ‘strictness’ without writing custom rules from scratch. Zero config needed if you’re already using PHPStan."*