sebastian/version
Library for deriving a PHP project’s version from Git. Provide a release string and project path; Version::asString() returns the release, a -dev suffix, or git describe output (tags/commits) depending on repo state and release format.
This package is fundamentally unusable due to its PHP 8.4 dependency (which doesn't exist) and future-dated release metadata. As a PM, I would reject it in all build-vs-buy decisions, recognizing that the core functionality (Git-based versioning) is trivial to implement internally with minimal risk. Roadmap planning would explicitly exclude this dependency, and use cases for version reporting would rely on simpler in-house solutions or maintained alternatives. The package represents a technical dead end with zero operational value.
Never. The PHP 8.4 requirement is impossible to satisfy (current stable versions are 8.2/8.3), and the 2026 release date indicates severe metadata corruption. With 0 direct dependents despite high stars, there is zero evidence of real-world adoption. Teams needing versioning should immediately look elsewhere—using built-in Composer versioning, custom scripts, or actively maintained libraries like composer/composer's version handling. This package should be avoided entirely due to its technical impossibility and lack of maintenance signals.
"This package is not a viable option—it requires PHP 8.4, which doesn't exist, making installation impossible. The future release date and zero dependents confirm it's inactive or misconfigured. Instead, we'll implement versioning using our existing CI/CD pipeline (e.g., Git tags and simple PHP scripts) which is more reliable and avoids dependency risks. This approach saves engineering time, ensures compatibility with our current stack, and eliminates unknown technical debt."
How can I help you explore Laravel packages today?