Sponsorship
PHPRegex is nineteen packages — a PCRE2-true parser, a linter, a ReDoS analyzer, and integrations for PHPStan, Psalm, Rector, PHPUnit, Infection, Laravel and Symfony — kept honest by a test suite that runs thousands of patterns against the real PCRE2 engine before every release.
PHPRegex is built and maintained by Younes ENNAJI — issues read, bugs fixed, every new PCRE2 release followed, these docs maintained with care. Sponsorship is what makes that time possible, and what keeps the project alive and independent. If it parses your patterns, guards your builds or saves your team debugging time, backing it is the way to make sure it stays that way.
In short
- Sponsoring goes through GitHub Sponsors, once or on a recurring basis, for the amount you choose. GitHub takes care of the payment and the receipt.
- A developer gets their name and avatar among the backers on every documentation page.
- A company gets its logo in the “Backed by” footer of every page.
- A company can also take a spot — a part of PHPRegex it backs alone for a whole release. The first to ask takes it.
- Once listed, always listed. The page is empty today, which is exactly why backing it now is the better deal: the first sponsors are the most visible, and they stay visible for good.
There is no price list: any amount, one-time or monthly, counts the same.
What you get
| You are | What you get |
|---|---|
| Anyone | Our thanks, and your name in BACKERS.md. GitHub adds a sponsor badge to your profile on its own. |
| A developer | Your name and avatar among the backers at the foot of every documentation page and in BACKERS.md, and a thank-you post on X. |
| A company | Your logo in the “Backed by” footer of every page, in the README and BACKERS.md, and a thank-you in the release notes. |
| A company with a spot | Everything above, plus a spot: your company alone on that part’s pages, and named in the README of its packages for the whole release. |
Spots
A spot is a part of PHPRegex that one company backs for a whole release — every version of PHPRegex 2.0, from the first to the last patch. All spots for 2.0 are founding spots: empty today, and the first company to ask for one takes it. Sponsor on GitHub and tell us which spot you want, or write first. While you hold a spot:
- The sponsor frame at the foot of every page of the spot shows your company alone, with your logo, your name and one line about what you do.
- The README of each of the spot’s packages names you. That README ships with the package: Composer installs it into the
vendor/folder of every project that requires it, and GitHub and Packagist show it on the package’s page. - Your logo joins the “Backed by” footer of every other page.
Core engine
Open for PHPRegex 2.0.
Every PHPRegex package installs php-regex/regex-parser, so this spot’s line rides in the README of every vendor/ folder that holds PHPRegex — and on the concept, internals and data pages of these docs.
- Packages:
php-regex/regex-parser,php-regex/regex-toolkit,php-regex/regex-explain,php-regex/regex-optimizer,php-regex/regex-generator,php-regex/regex-transpiler,php-regex/regex-automata - Pages: /concepts/, /concepts/ast/, /concepts/visitors/, /concepts/pcre/, /concepts/how-pcre2-matches/, /nodes/, /visitors/, /architecture/, /design/ast-traversal/, /extending/, /reference/api/, /reference/capture-shapes/, /reference/pattern-info/, /reference/prefilters/, /reference/logic-solver/, /reference/pcre2-conformance/, /reference/feature-support-matrix/, /reference/correctness-contracts/, /reference/extraction-coverage/
Linter & ReDoS
Open for PHPRegex 2.0.
The pages a team reads when a pattern fails its build: every diagnostic, the rules, the ReDoS guide and the CLI. Twelve PHPRegex packages install php-regex/regex-redos, and its README names this spot’s company.
- Packages:
php-regex/regex-linter,php-regex/regex-redos,php-regex/regex-cli - Pages: /reference/rules/, /reference/diagnostics/, /reference/diagnostics-cheatsheet/, /reference/sonar/, /reference/json-output/, /guides/redos/, /concepts/redos/, /guides/cli/, /adding-a-lint-rule/
Education
Open for PHPRegex 2.0.
The ten chapters of the regex tutorial, the cookbook and the PHP regex guide: the pages a developer reads to learn regular expressions, from the first pattern to ReDoS.
Integration spots
One package and one guide each, held the same way — your company alone on the guide’s pages and in the package’s README:
-
PHPStan integration —
php-regex/regex-phpstan, the PHPStan integration guide. -
Psalm integration —
php-regex/regex-psalm, the Psalm integration guide. -
Rector integration —
php-regex/regex-rector, the Rector integration guide. -
PHPUnit integration —
php-regex/regex-phpunit, the PHPUnit integration guide. -
Infection integration —
php-regex/regex-infection, the Infection integration guide. -
Laravel integration —
php-regex/regex-laravel, the Laravel integration guide. -
Symfony integration —
php-regex/regex-symfony, the Symfony integration guide. -
Language server —
php-regex/regex-language-server, the Language server guide. -
MCP server —
php-regex/regex-mcp, the MCP server guide.
Backers
The developers who back PHPRegex line the foot of the sponsor frame on every documentation page, with their GitHub avatar, and are listed in BACKERS.md. When you join, we thank you in a post on X. Your name, your avatar, at the foot of every page of the documentation you use — that is the point.
How long it lasts
- It lasts the whole release. From the moment you join — all we need is a logo, a link, and for a spot one line about your company — your name rides every version of PHPRegex 2.0, and the versions that ship keep it for good. The holder of a spot is asked first when the next release opens.
- Nobody is ever taken off. Names in BACKERS.md, avatars among the backers, logos in the footer stay, even after a sponsorship ends.
What to send
Reply to the welcome email GitHub sends, or write to [email protected], with:
- your logo as SVG, or PNG at least 400 pixels wide, and a variant for dark backgrounds if you have one;
- the address it should link to;
- for a spot, which spot, and one line about your company, 120 characters at most.
Questions
Write to [email protected] — or sponsor PHPRegex now, it takes a minute. For the people and companies who already back the project, see BACKERS.md.