phar-io/version

Library for handling version information and constraints

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 49 minutes ago
Added to GitGenius on September 8th, 2026
Created on November 30th, 2016
Open Issues & Pull Requests: 5 (+0)
GitHub issues: Enabled
Number of forks: 18
Total Stargazers: 7,462 (+0)
Total Subscribers: 4 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.1 hours
Mean response time: 0.1 hours
90th percentile: 0.1 hours
Tracked items: 1

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 736 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

PharIO Version is a PHP library for handling version information and constraints.

The library solves the problem of parsing, comparing, and validating semantic versions and version ranges in PHP applications. It works by accepting version strings and constraint expressions, then determining whether specific versions fall within those constraints. The library supports semantic versioning format with major, minor, and patch components, and provides special operators for common version range patterns: the caret operator to match versions within a major version boundary, and the tilde operator to match versions within a minor version boundary. Pre-release labels are factored into version comparisons.

Developers should choose this library when building PHP applications that need to validate or filter versions against specified ranges, such as dependency management systems, package managers, or version-aware configuration tools. It suits projects that work with semantic versioning and need to express flexible version requirements. The library can be installed as either a production or development-time dependency depending on whether version handling is needed at runtime or only during testing and tooling.

The project maintains a focused scope on version constraint handling without attempting to solve broader dependency resolution problems. Development activity shows consistent attention to the core functionality, with updates addressing version comparison logic and pre-release label handling.