- Is this package still maintained? Should I use it in Laravel projects?
- No, this package is abandoned since 2015. The original author recommends using the maintained fork at **php-parallel-lint/PHP-Parallel-Lint** instead. For Laravel, consider alternatives like **php-parallel-lint** or **roave/security-advisories** for modern linting needs.
- How do I install PHP Parallel Lint in a Laravel project?
- Run `composer require --dev jakub-onderka/php-parallel-lint` in your Laravel project root. For colored output, also install `jakub-onderka/php-console-highlighter`. Note: This is a legacy tool—prefer the maintained fork for new projects.
- Does this work with Laravel’s PHP version (8.x)?
- The package officially supports PHP ≥5.4.0, but it was last updated in 2015. Test thoroughly in PHP 8.x, or use the maintained fork (**php-parallel-lint/PHP-Parallel-Lint**), which supports modern PHP versions and includes security fixes.
- How do I exclude Laravel’s `vendor/` and `node_modules/` directories?
- Use the `--exclude` flag multiple times: `vendor/bin/parallel-lint --exclude vendor --exclude node_modules .`. This prevents scanning third-party dependencies, which is critical for Laravel projects to avoid false positives.
- Can I integrate this into Laravel’s CI pipeline (GitHub Actions, GitLab CI)?
- Yes, but use the `--checkstyle` or `--json` flag for machine-readable output. Example: `vendor/bin/parallel-lint --json --exclude vendor . > lint-results.json`. For CI, the maintained fork is safer due to active updates and compatibility.
- What’s the performance difference vs. running `php -l` manually?
- PHP Parallel Lint can be **20x faster** for large codebases by running parallel jobs (adjustable with `-j`). For a Laravel app with 1,000+ files, this tool significantly reduces CI wait times compared to serial `php -l` checks.
- Does it support Git blame for failed lines in Laravel?
- Yes, use `--blame` to show Git blame info for failing lines. Example: `vendor/bin/parallel-lint --blame src/`. This helps track who introduced syntax errors in Laravel’s codebase.
- Are there security risks using this abandoned package?
- Yes, abandoned packages may have unpatched vulnerabilities (e.g., PHP-CGI injection risks). Avoid passing untrusted paths to `-p` (PHP-CGI). For Laravel, prioritize the maintained fork or alternatives like **php-parallel-lint**, which include security updates.
- Can I use this for static analysis in Laravel (e.g., SonarQube)?
- Yes, generate Checkstyle XML (`--checkstyle`) or JSON (`--json`) for integration with SonarQube or other tools. However, this package only checks syntax—not coding standards (e.g., PSR-12). For full static analysis, combine it with **PHPStan** or **Psalm**.
- What’s a good alternative for Laravel if this package is abandoned?
- Use the maintained fork: **php-parallel-lint/PHP-Parallel-Lint** (same name, different repo). Other Laravel-friendly alternatives include **roave/security-advisories** (for security checks) or **dealerdirect/phpcodesniffer-composer-installer** for PSR compliance.