PatchPub is a Laravel-based platform designed to centrally manage and apply patches to PHP Composer packages. It allows developers to apply their own fixes or features directly to third-party packages — whether or not they’ve been merged upstream. PatchPub makes it easy to manage targeted changes in dependencies in an efficient, traceable, and version-safe way. With features like regex patching, git diff previews, and GitHub pull request imports, it fills a crucial gap in the Composer ecosystem.
URL: https://patchpub.com
Functionalities in detail
Core Features & Architecture
🧱 Technical Foundation:
- Laravel + Laravel Livewire:
The admin and user interfaces are built with Livewire, delivering a reactive, seamless browser-based experience. - SQLite for lightning-fast data access:
Internal data queries are optimized for speed using SQLite, ideal for lightweight and mid-sized patch management workflows. - Cloudflare R2:
All relevant patch data and file versions are stored in Cloudflare R2 for maximum reliability and independence from the app infrastructure.
Powerful Patch Capabilities
🛠️ Flexible Editing Options for Any File (incl. composer.json):
- Simple text search & replace
- Regex-based replacements
- Classic diff patch application
- Full file replacement
- Chaining of multiple operations in defined order
🔁 Automated Patch Management:
- GitHub PR Import:
Easily pull in public GitHub Pull Request patches directly into PatchPub. - Preview via git diff:
Full visual diff before applying changes ensures transparency and control. - Change validation:
All operations are pre-validated to prevent broken patch applications. - Asynchronous background processing (queues):
Patch applications and updates — especially for new dependency versions — are handled in the background, keeping the UI responsive at all times.
📬 Notifications & Monitoring:
- Automatic email notifications alert users when patches fail due to incompatible changes in new versions (e.g. modified source files).
- This ensures proactive responses to deprecated or broken patches.
Use Cases:
- Applying custom bugfixes or features to third-party packages
- Temporary hotfixes without needing to fork dependencies
- Reusable patch sets for teams or organizations
- Automated patch updates on version bumps
- Email Notifications on patch failures