Download the PHP package yoeunes/regex-parser without Composer
On this page you can find all versions of the php package yoeunes/regex-parser. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download yoeunes/regex-parser
More information about yoeunes/regex-parser
Files in yoeunes/regex-parser
Package regex-parser
Short Description A powerful PCRE regex parser with lexer, AST builder, validation, ReDoS analysis, and syntax highlighting. Zero dependencies, blazing fast, and production-ready.
License MIT
Homepage https://github.com/yoeunes/regex-parser
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package regex-parser
RegexParser: Static Analysis, Linter & Logic Solver
RegexParser is a PHP 8.2+ library that treats regular expressions as code.
Unlike simple wrappers around preg_match, RegexParser implements a complete compiler pipeline (Lexer → Parser → AST) and an Automata-based Logic Solver (AST → NFA → DFA).
This architecture allows for advanced static analysis:
- Linting: Detect redundancy, useless flags, and common mistakes.
- Safety: Statically detect potential catastrophic backtracking (ReDoS).
- Logic: Compare patterns via NFA/DFA (Intersection, Equivalence, Subset) for the regular subset it supports.
Built for learning, validation, and robust tooling in PHP projects.
⚠️ What this is and is not. RegexParser is a side project and a learning exercise. It is not a hardened security product and should not be your only line of defense. ReDoS detection is structural and conservative — treat findings as potential risk to investigate, not as a guarantee of safety. The parser aims for PCRE compatibility but does not cover every edge case of the PCRE engine.
If you are new to regex, start with the Quick Start Guide.
Getting started
What RegexParser provides
- 🏗️ Deep Parsing: Parse
/pattern/flagsinto a structured, typed AST. - 🧠 Logic Solver: Compare two regexes using NFA/DFA transformation (intersection, equivalence, subset). Works for patterns in the regular subset it supports; falls back gracefully otherwise.
- 🛡️ ReDoS Analysis: Detect potential catastrophic backtracking risks structure-wise. Findings are heuristic — treat them as risk to investigate, not a guarantee.
- 🧹 Linter: Detect useless flags, redundant groups, and common mistakes via the CLI.
- 📖 Explanation: Explain patterns in plain English.
- 🔧 Visitor API: A flexible API for building custom regex tooling.
Philosophy & Accuracy
RegexParser separates what it can guarantee from what is heuristic:
- Guaranteed: parsing, AST structure, error offsets, and syntax validation for the targeted PHP/PCRE version.
- Heuristic: ReDoS analysis is structural and conservative; treat it as potential risk unless confirmed.
- Context matters: PCRE version, JIT, and backtrack/recursion limits change practical impact.
Tested against the real engine
Round-trip correctness (compile(parse(x)) behaves like the original) is
verified in CI by differential tests that compare RegexParser's output against
PHP's native preg_match():
- A fixture of 212 PCRE patterns is checked for validity, match result,
and captured groups (
OfficialPcreComplianceTest). - Additional behavioral tests cover named groups, lookarounds, conditionals,
atomic groups, and other features (
BehavioralComplianceTest,AdvancedFeaturesComplianceTest).
These tests compare against a limited set of subjects, so they catch clear regressions but are not a formal proof of full PCRE equivalence. There may be edge cases that the test suite does not yet cover.
Separately, the linter and ReDoS analyzer have been run over a corpus of
~960 unique patterns collected from 279 real-world PHP projects (Symfony,
Laravel, Composer, PHPUnit, …). The results are in corpus/corpus.log and
corpus-redos.log. This corpus run is not part of the automated CI
differential test — it is a snapshot used to validate that the lint and ReDoS
rules produce sensible output on real code.
How to report a vulnerability responsibly
If you believe a pattern is exploitable:
- Run confirmed mode and capture a bounded, reproducible PoC.
- Include the pattern, input lengths, timings, JIT setting, and PCRE limits.
- Verify impact in the real code path before filing a security issue.
See SECURITY.md for reporting channels.
Safer rewrites (verify behavior)
These techniques reduce backtracking but can change matching behavior. Always validate with tests.
How it works
Regex::parse()splits the literal into pattern and flags.- The lexer produces a token stream.
- The parser builds an AST (
RegexNode). - Visitors walk the AST to validate, explain, analyze, or transform.
For the full architecture, see docs/ARCHITECTURE.md.
CLI quick tour
PHP API at a glance
Integrations
RegexParser integrates with common PHP tooling:
- Symfony bundle: docs/guides/cli.md
- PHPStan:
vendor/yoeunes/regex-parser/extension.neon - GitHub Actions:
vendor/bin/regex lintin your CI pipeline
Performance
RegexParser ships lightweight benchmark scripts in benchmarks/ to track parser, compiler, and formatter throughput.
- Run formatter benchmarks:
php benchmarks/benchmark_formatters.php - Run all benchmarks:
for file in benchmarks/benchmark_*.php; do echo "Running $file"; php "$file"; echo; done
Documentation
Start here:
- Docs Home
- Quick Start
- Tutorial
Key references:
- Architecture
- API Reference
- Diagnostics
- FAQ & Glossary
Contributing
Contributions are welcome! See CONTRIBUTING.md to get started.
License
Released under the MIT License.
Support
If you run into issues or have questions, please open an issue on GitHub: https://github.com/yoeunes/regex-parser/issues.
