GitPulse is an open-source dashboard designed to analyze and contextualize developer activity and contribution trends within a GitHub organization.

I started building it as a CTO because I couldn't find a tool that was simple and reliable enough to truly understand the work of my teams and products. Most analytics tools are focused on superficial vanity metrics and risk turning into tools for surveillance. GitPulse is different. It’s an analytical tool to drive a culture of performance, not a tracking tool for surveillance. It’s built to foster transparency and dialogue, and to help teams grow by valuing real impact over simple activity.

GitPulse is a personal project, developed during my free time. It will evolve based on my availability and interests. Unlike most solutions that focus on repository-level data, GitPulse lets you group multiple repositories into a single logical project—reflecting how real software is built and delivered. This holistic approach is perfect for tracking large apps, microservices, or monorepo-like architectures.

I'm currently building GitPulse solo, with no QA team. If you encounter bugs or unexpected behavior, contributions are welcome—as long as they stay aligned with the spirit of the project: useful, readable, and not overengineered.

🚨 GitPulse is under alpha dev process, i can introduce breaking changes

Comprehensive documentation is available at: https://assiadialeb.github.io/gitpulse/

1. Read the contribution guide
2. Fork the repository
3. Create a feature branch
4. Make your changes
5. Add tests if applicable
6. Submit a pull request

You can also use to ask questions about code, data structure...

This project is licensed under the GNU Affero General Public License v3.0 (AGPLv3).

If you encounter any issues:

1. Check the documentation
2. Search existing issues
3. Create a new issue with detailed information
4. Discuss with the community