edgurgel/poxa
This system is a WebSocket-based event broadcasting service, likely implementing the Pusher protocol, designed to manage real-time channel subscriptions and presence tracking. It provides a pluggable architecture for handling connections, managing channel state, and dispatching webhooks, all configurable via environment variables. The system includes a web-based console for monitoring events and is supported by comprehensive test coverage for its core modules and integration scenarios.
56.7
Adequate · 1 August 2026
1.7k
lines of production code
Elixir
with JavaScript
1
bus factor · 26 authors in all
3
measurements over time
How it got here
2013 · Modernization and dependency upgrade
This period focused on modernizing the Poxa codebase by upgrading to Elixir 1.16 and migrating dependencies to Hex packages. The work included refactoring the registry abstraction, updating the startup process to use the modern Elixir Application API, and replacing legacy logging with the built-in Logger. Additionally, comprehensive tests were added for core modules, and a Dockerfile was introduced to support containerized releases.
5 changes
2014 · Console interface and configuration modernization
This period focused on enhancing the Poxa application with a new web-based console for monitoring real-time events, supported by comprehensive integration and unit tests. The work also modernized the internal architecture by refactoring the console handler to use the Cowboy 2 API and centralizing configuration via environment variables.
6 changes
2016–2019 · Webhook architecture and release configuration
This period focused on refactoring the webhook delivery system into a dedicated supervisor tree with separate handler and dispatcher processes, supported by comprehensive test coverage. Additionally, release environment configuration templates were added to facilitate deployment across different operating systems.
4 changes
Survey your own repository
edgurgel/poxa was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 1 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 141c310776 — the exact code this score is about.
- Scored under rubric rubric-2026.08.18. Score the same commit under that rubric and you get the same number.