phar-io/manifest

Component for reading phar.io manifest information from a PHP Archive (PHAR)

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 47 minutes ago
Added to GitGenius on September 8th, 2026
Created on November 24th, 2016
Open Issues & Pull Requests: 5 (+0)
GitHub issues: Enabled
Number of forks: 15
Total Stargazers: 7,474 (+0)
Total Subscribers: 3 (+0)

Repository Insights (GitGenius)

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

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

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: 1,186 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

Manifest is a PHP library component for reading phar.io manifest information from PHP Archive files.

The tool solves the problem of parsing and accessing metadata stored in PHAR manifest files. It provides a structured way to read manifest.xml data from PHP Archives, allowing developers to programmatically extract phar.io manifest information rather than handling raw XML parsing themselves. The library can be used both to read existing manifest files and to create manifests via an API.

Developers building tools that work with PHAR files, particularly those in the phar.io ecosystem, should adopt this library. It suits projects that need to inspect or validate PHAR metadata, such as package managers, build tools, or distribution systems. The library is available as both a production and development-time dependency through Composer, making it flexible for different use cases.

The project maintains active engagement with its codebase, accepting pull requests and responding to issues. Development activity shows consistent attention to the repository with regular updates and community contributions being reviewed and integrated.