Mediawiki Phan Config Laravel Package

Product Decisions This Supports

• Build vs. Buy: Eliminates the need to build and maintain a custom Phan configuration from scratch for MediaWiki projects, saving engineering time and reducing technical debt.
• Code Quality Standardization: Ensures consistent static analysis across extensions/skins by enforcing MediaWiki-specific coding standards, security checks (via taint analysis), and best practices out-of-the-box.
• CI/CD Integration: Streamlines adoption of automated code analysis in continuous integration pipelines (e.g., Jenkins, GitLab CI), aligning with Wikimedia’s existing tooling ecosystem.
• Roadmap Prioritization: Identifies critical bugs and vulnerabilities early in development, enabling teams to focus on high-impact technical debt and feature delivery.

When to Consider This Package

• Adopt when: Your project is a MediaWiki extension, skin, or PHP library tightly integrated with MediaWiki’s ecosystem, and you require standardized static analysis using Phan with taint checking.
• Look elsewhere when: Your project is unrelated to MediaWiki (e.g., standalone PHP apps), uses alternative static analysis tools (PHPStan, Psalm), or lacks compatibility with Phan 6.0+ and PHP 8.1+. Avoid if your team prioritizes flexibility over MediaWiki-specific conventions or operates outside Wikimedia’s contributor guidelines.

How to Pitch It (Stakeholders)

This pre-configured Phan setup for MediaWiki projects eliminates manual configuration efforts, ensuring consistent code quality and security compliance across extensions and skins. For executives, it reduces technical debt and accelerates delivery by catching issues early; for engineers, it provides a battle-tested, integrated solution that works out-of-the-box with your CI/CD pipeline, so you can focus on innovation rather than tooling setup.