theseer/tokenizer

A small library for converting tokenized PHP source code into XML (and potentially other formats)

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 45 minutes ago
Added to GitGenius on September 13th, 2026
Created on April 5th, 2017
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Enabled
Number of forks: 25
Total Stargazers: 5,192 (+0)
Total Subscribers: 8 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.4 hours
Mean response time: 35.8 hours
90th percentile: 9.3 days
Tracked items: 7

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 10% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Tokenizer is a PHP library that converts tokenized PHP source code into XML.

The library solves the problem of transforming PHP's native token stream into a structured XML representation. It takes PHP source code that has been tokenized by PHP's built-in tokenizer and converts it into an XML format, making the token structure more accessible for parsing, analysis, and manipulation by tools that work with XML.

Developers should choose this library when building tools that need to analyze or process PHP code structure in a machine-readable format. It suits projects that perform static analysis, code transformation, or code generation on PHP files, particularly those that already have XML processing pipelines in place. The library is available as both a standard dependency and a development-time dependency through Composer, making it flexible for inclusion in different project contexts.

The project maintains a stable codebase with infrequent commits, indicating a mature tool that has reached a stable state. Pull requests are reviewed and merged, showing ongoing maintenance and responsiveness to contributions. The project has not adopted a rapid release cycle, reflecting its position as a focused utility with a well-defined scope.