Hidev Phpstan Laravel Package

Product Decisions This Supports

• Integration with HiDev for PHPStan: Enables seamless static analysis within the HiDev ecosystem, reducing friction for teams already using HiDev (a code generation/automation tool). This supports a build vs. buy decision by leveraging existing HiDev infrastructure rather than standalone PHPStan setups.
• Developer Productivity: Aligns with roadmap items focused on automated code quality checks in CI/CD pipelines or local development. Reduces manual configuration overhead for PHPStan by integrating it into HiDev’s workflow.
• Legacy System Modernization: Useful for teams maintaining older Laravel/PHP codebases where HiDev is already adopted, enabling incremental adoption of static analysis without disrupting existing tooling.
• Custom Rule Enforcement: Supports enforcing team-specific coding standards via PHPStan rules, particularly for projects where HiDev’s code generation templates require validation.

When to Consider This Package

• Adopt if:

  • Your team already uses HiDev for code generation/automation and seeks to integrate PHPStan without standalone setup.
  • You prioritize minimal configuration for static analysis in a Laravel/PHP environment.
  • Your roadmap includes automated quality gates tied to HiDev’s workflow (e.g., pre-commit hooks or CI pipelines).
  • You’re maintaining a legacy Laravel/HiDev codebase and want to modernize with static analysis.

• Look elsewhere if:

  • You’re not using HiDev—this package lacks standalone value and requires HiDev as a dependency.
  • You need advanced PHPStan features (e.g., custom rules, deep framework integration) beyond basic checks; consider native PHPStan or laravel-stan.
  • Your team prefers modern tooling (e.g., PestPHP, Rector) over HiDev’s legacy ecosystem.
  • The package’s last release (2020) is a red flag for long-term maintenance; evaluate risk tolerance.

How to Pitch It (Stakeholders)

For Executives: "This plugin lets us bake PHPStan static analysis directly into HiDev’s existing workflow—no extra tools or setup. It’s a lightweight way to catch bugs early, especially for teams already using HiDev for code generation. Think of it as ‘autopilot’ for code quality: HiDev generates the code, and PHPStan verifies it before deployment. Low risk, high upside for maintaining our legacy Laravel systems."

For Engineering: *"If we’re using HiDev, this drops PHPStan into our pipeline with zero extra configuration. It’s a thin wrapper that lets us run static analysis as part of HiDev’s commands (e.g., hidev run phpstan). Ideal for:

• CI/CD: Add hidev phpstan to your build steps.
• Local dev: Run checks alongside hidev generate.
• Legacy code: Validate generated templates without manual PHPStan setup. Downside: Limited to HiDev users, and the package is stale (last updated 2020). If we’re all-in on HiDev, it’s a no-brainer; otherwise, we should stick with native PHPStan or laravel-stan."*

For Developers: "This is a 5-minute setup if you’re already using HiDev. Just composer require hiqdev/hidev-phpstan, and you can run PHPStan via hidev phpstan. It’s not a replacement for full PHPStan—just a way to tie static analysis into HiDev’s commands. Perfect for teams that want to avoid managing separate tools."