Open-Source Contributions

Open-source contributions across PHP, Laravel, Vue.js and AI tooling

Our team contributes to the open-source ecosystems we build on every day: PHP and Laravel, Vue.js, TigerBeetle, Warp and a wide range of AI and automation tools. The pattern is consistent. When a dependency breaks or falls short in production, we fix it where the fix belongs and send it upstream. When we build something reusable, we publish it.

This page collects the public side of that work: pull requests to upstream projects, bug reports, research on infrastructure we evaluate, and our own open-source repositories.

Upstream pull requests and issues

• Filament (Laravel) — Filament is the admin-panel and UI framework we use for Laravel back offices, including Bronjoy's. Its tabs were aligned vertically but not centered horizontally, so we added justify-center to the tab item Blade template and documented the change with before-and-after screenshots. The pull request was merged in November 2024.
• DoctrineBundle (Symfony and PHP) — in February 2024 we proposed a fix for multiple definitions in the Symfony bundle for Doctrine ORM and DBAL. It was closed without being merged.
• Chart.js range-select plugin (JavaScript) — a small plugin for draggable range selection on Chart.js charts. We added checks so it works inside reactive front-end frameworks, the kind behind the Vue.js dashboards we ship, and the change was merged in January 2025.
• hh-applicant-tool (Python and AI) — a popular open-source CLI that automates job applications on HH.ru, including AI-generated cover letters. While deploying it in Docker on a fresh server, we found that HH.ru had renamed the password-login button and that the first OAuth page load from a new server IP took 30–45 seconds. Our fix for the selector and the navigation timeout was merged in July 2026. A second, larger pull request proposed reliability fixes for AI cover letters and employer replies, including a bug that could re-send messages into unread chats on every cron run. It was closed without being merged. The full story is in our job-application automation case study.
• Warp (terminal) — as Warp users on Linux, we reported a bug on Ubuntu 24.04 where selecting text from earlier command output highlighted the wrong characters even though the copied text was correct. It was closed as not planned.

TigerBeetle and ledger infrastructure

Our TigerBeetle work has been exploration and knowledge sharing rather than code. We explored TigerBeetle, a database built specifically for financial transactions, and published a write-up of what stood out: double-entry correctness (debits equal credits) enforced by the database itself, built-in audit trails and immutability, and an operational philosophy that favors simplicity, down to recommending systemd over Docker. It is the kind of evaluation we do before recommending infrastructure for fintech products.

Our own open-source projects

• Starter kits — a Laravel JWT authentication API starter under the MIT license and a matching Vue JWT authentication starter for fast prototyping, plus a Laravel enterprise API reference architecture that documents layered, domain-driven patterns.
• Developer CLIs and utilities — openapi-domainify, a CLI that splits an OpenAPI spec into domain-based TypeScript service classes instead of one monolithic generated file, and a Laravel console command that parses XML and JSON inside directories and zip or gzip archives.
• Laravel ecosystem patches — a public, patched copy of the Filament plugin for Vemto, the Laravel code generator, with its livewire/livewire dependency removed.
• Telegram — Finfolio, an MIT-licensed Telegram Mini App starter in plain JavaScript.
• AI tools from hackathons — five MIT-licensed tools built and demoed at the AMD Developer Hackathon in July 2026: Keystone, a decision engine where an LLM proposes, a solver decides and a verifier certifies; RecipeReel, which turns cooking videos into structured recipes; LectureLoom, which turns lecture videos into study notes; Legible, for AI document accessibility remediation; and Testify, for compliance auditing of regulated phone calls. Our UM Hackathon 2026 project, Opus Magnum, is public too.
• A public club codebase — Pitch, the Next.js and Supabase tournament platform behind the XCeed Football Cup, is developed in a public repository where we merged our tournament lifecycle, scorekeeper and row-level security work.

How we work in open source

• Fix where the fix belongs. A local patch to vendored code is wiped by the next upgrade. An upstream fix protects every user, including us.
• Reproduce first. Our pull requests describe the failure, how we reproduced it and how the fix was tested, for example against a real account from a fresh server IP.
• Show the full record. Not every pull request gets merged, and we list those here too.
• Publish what is reusable. Starter kits, CLIs and hackathon tools go out under permissive licenses where we can.

Related work

This open-source experience feeds directly into client work: Laravel and Filament back offices in our web app development projects, and AI tooling in AI integration and automation. For a closer look at one contribution in production, see job-application automation.