Coverage Laravel Package

Product Decisions This Supports

• Decide whether Codacy should remain the system of record for PHP/Laravel test coverage and quality reporting; this package only matters if Codacy is already strategic.
• Build vs. buy: avoid building a custom coverage uploader for Laravel CI. Use a maintained vendor reporter or a broader coverage platform instead.
• Migration planning: identify legacy Laravel/PHP repositories still using codacy/coverage and replace it with a supported path such as codacy-coverage-reporter.
• CI quality-gate decisions: coverage uploads can support PR coverage visibility, badges, and trend reporting, but only if the upload mechanism is maintained and reliable.
• Roadmap prioritization: treat this package as a deprecation/cleanup item, not a new capability. New Laravel services should not standardize on it.

When to Consider This Package

• Only consider it for legacy PHP projects already using Codacy and old CI scripts that explicitly depend on codacy/coverage.
• Use it only as a temporary bridge while migrating to codacy-coverage-reporter or another maintained coverage tool.
• Look elsewhere for new Laravel/PHP projects, modern PHP versions, active security maintenance, and long-term CI support.
• Look elsewhere if the team needs GitHub Actions-native coverage, Codecov, Coveralls, SonarQube/SonarCloud, or a vendor-supported Codacy integration.
• Avoid adoption given the package is archived, deprecated, last released in January 2020, and has no dependent packages listed.

How to Pitch It (Stakeholders)

This package is deprecated and should not be adopted for new Laravel/PHP work. Codacy’s own README points users to codacy-coverage-reporter, so the product recommendation is migration rather than investment. For executives, the message is risk reduction: remove an archived dependency while preserving coverage visibility through a maintained reporter or alternative platform. For engineering, the message is operational: do not add codacy/coverage to new services; replace it in legacy pipelines, validate PHPUnit Clover output and Codacy tokens, and confirm coverage still appears in PRs before removing the old dependency.