psalm/phar
Install Psalm as a standalone PHAR to avoid Composer dependency conflicts. psalm/phar lets you add Psalm to any project or CI environment without pulling in extra packages, keeping your dependency tree clean while still running Psalm reliably.
Architecture fit is suboptimal for modern Laravel projects due to the package's outdated state (last release Aug 2021) and lack of alignment with Psalm's current recommendations. While PHARs avoid Composer dependency conflicts, this specific package conflicts with Psalm's official guidance to use vimeo/psalm directly. Integration feasibility is low due to PHP 8.2+ requirement mismatch for legacy projects and potential feature gaps in the stale PHAR version. Technical risks include unpatched security vulnerabilities, inability to parse modern PHP syntax (e.g., PHP 8.3 features), and broken compatibility with current Laravel tooling. Key questions: Is this package officially deprecated? Why does Psalm's documentation now prioritize direct vimeo/psalm installation over this PHAR? How does this package differ from the official Psalm PHAR download?
Stack fit is poor—Laravel's ecosystem expects Composer-managed dev dependencies (e.g., vimeo/psalm), and this PHAR package introduces unnecessary indirection with no clear benefit. Migration path should avoid this package entirely; instead, migrate to vimeo/psalm via Composer (composer require --dev vimeo/psalm) or official PHAR download. Compatibility risks include missing support for Laravel 10+ PHP 8.2+ features (e.g., typed properties in attributes) and plugin system incompatibilities. Sequencing should skip this package entirely; if static analysis is needed, prioritize the maintained vimeo/psalm package with CI integration steps aligned to current Psalm documentation.
Maintenance burden is high due to zero recent releases and no community activity—bug fixes or security patches won't be backported. Support is nonexistent (0 dependents, stale GitHub issues), forcing teams to troubleshoot issues without upstream assistance. Scaling risks include unoptimized performance for large codebases (older Psalm versions lack modern parallelization improvements) and incorrect error reporting for modern PHP syntax. Failure modes include silent analysis failures on PHP
How can I help you explore Laravel packages today?