This project has been archived by its maintainers, and is no longer receiving any updates.
GitPowerDash 🚀
Empowering Executive Oversight through Git Analytics and Graph-based Star Schemas.
gitpowerdash is a lightweight Python CLI and library designed to bridge the gap between technical development history and executive-level project management. It transforms raw Git logs into a structured Star Schema, available as local CSVs or hydrated directly into a Microsoft Fabric Graph.
🚀 The Value Proposition
Traditional Git viewers are built for developers. gitpowerdash is built for Decision Makers.
📊 The Star Paradigm
Whether you use CSVs or the Graph, the data is modeled for analytical performance:
-
Dimensions (Nodes):
AuthorandFileentities. -
Facts (Edges):
Commitsthat link Authors to Files, containing quantitative measures likeInsertionsandDeletions.
🛠️ Installation
Bash
git clone https://github.com/youruser/gitpowerdash
cd gitpowerdash
uv sync
📖 Usage
1. Direct CSV Export (Local Power BI)
The fastest way to get started. Generates a "Fact" and "Dimension" table structure in the ./export folder.
Bash
uv run gitpowerdash extract --output ./export
2. Fabric Graph Hydration (Cloud Intelligence)
To move beyond flat files and perform complex path-analysis in Fabric:
A. Configure Identifiers (Stored securely in OS Keyring):
Bash
uv run gitpowerdash configure
B. Login (Device Code Flow):
Bash
uv run gitpowerdash login
C. Hydrate (Transform and Push):
Bash
uv run gitpowerdash hydrate --workspace-id <fabric-workspace-uuid>
🚀 Why Use the Graph?
While CSVs are great for basic velocity, Hydrating the Fabric Graph allows you to:
-
Identify Knowledge Silos: Query paths to find files touched by only one author.
-
Analyze Blast Radius: See which contributors are most "connected" to a failing module.
-
Native Power BI Integration: Fabric Graph items are automatically available as Semantic Models.
🔒 Security
gitpowerdash follows professional security standards:
-
No Hardcoding: All Azure/Fabric IDs are user-configured.
-
Keyring Storage: MSAL Token Caches and secrets are stored in your OS-native secure vault.
-
Typing: Full Python type-hinting for robust integration.
Metadata
Release files for gitpowerdash 0.1.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| gitpowerdash-0.1.8.tar.gz | 8.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gitpowerdash-0.1.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 19.9 kB
Release files / gitpowerdash-0.1.8.tar.gz
| Download URL | gitpowerdash-0.1.8.tar.gz |
|---|---|
| Size | 8.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8b8b49e0ba952fbbd17bcf5cc935633a94030ede91a59727f8fa6e104ffc1e6d
|
|
BLAKE2b-256 checksum How to use checksums |
c5542c727546abdae06c9d45a9250e3d13a548ca853327a22afb97ba7c25e9c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 2, 2026.
Transparency logRelease files / gitpowerdash-0.1.8-py3-none-any.whl
| Download URL | gitpowerdash-0.1.8-py3-none-any.whl |
|---|---|
| Size | 10.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6333f0fc338e29744e27d1b3fec77275510fdc01392a8e804c03d77c50be28bf
|
|
BLAKE2b-256 checksum How to use checksums |
b7189d1c6153b5c2229af7ea3bf7ef1907729cb8df18e0dcd63c23dc016b2555
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 2, 2026.
Transparency log