code-maat-python 0.1.0__tar.gz → 0.2.0__tar.gz

code_maat_python-0.2.0/PKG-INFO

@@ -0,0 +1,134 @@
+Metadata-Version: 2.4
+Name: code-maat-python
+Version: 0.2.0
+Summary: Modern Python tool for mining and analyzing version control system data
+License: GPL-3.0
+License-File: LICENSE
+Keywords: vcs,git,analysis,mining,coupling,churn
+Author: Cameron Yick
+Author-email: cameron.yick@gmail.com
+Requires-Python: >=3.10,<4.0
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: GNU General Public License v3 (GPLv3)
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development :: Version Control
+Requires-Dist: click (>=8.1.0,<9.0.0)
+Requires-Dist: pandas (>=2.0.0,<3.0.0)
+Requires-Dist: python-dateutil (>=2.8.0,<3.0.0)
+Project-URL: Homepage, https://github.com/hydrosquall/code-maat-python
+Project-URL: Repository, https://github.com/hydrosquall/code-maat-python
+Description-Content-Type: text/markdown
+
+# code-maat
+
+[![License: GPL-3.0](https://img.shields.io/badge/License-GPL%203.0-blue.svg)](https://opensource.org/licenses/GPL-3.0)
+[![Python: 3.10+](https://img.shields.io/badge/python-3.10+-blue.svg)](https://www.python.org/downloads/)
+
+A Python implementation of [Code Maat](https://github.com/adamtornhill/code-maat) by Adam Tornhill. Analyzes Git repository history to identify code coupling, change patterns, and team dynamics.
+
+## Overview
+
+code-maat extracts insights from version control history:
+
+- Temporal coupling: Files that change together frequently
+- Code churn: Change frequency and stability metrics
+- Knowledge distribution: Contributor patterns and code ownership
+- Team coordination: Communication needs inferred from code changes
+
+These analyses help identify architectural dependencies not visible in static code structure, inform code review priorities, and understand how teams interact with code over time.
+
+## Why Use This Tool?
+
+Version control history contains information about code dependencies that aren't captured by static analysis. Files that frequently change together often share hidden coupling through business logic, data structures, or implicit contracts, even when they don't import each other directly.
+
+Research shows that files with high temporal coupling have 2-10x higher defect rates ([Predicting Faults from Cached History, MSR 2008](https://dl.acm.org/doi/10.1145/1453101.1453106)). Understanding these patterns helps with:
+
+- Prioritizing code review effort on coupled changes
+- Identifying coordination requirements between team members
+- Finding knowledge silos and ownership concentration
+- Discovering stable versus volatile areas of the codebase
+
+## Installation
+
+```bash
+# Using pip
+pip install code-maat
+
+# From source with Poetry
+git clone https://github.com/hydrosquall/code-maat.git
+cd code-maat
+poetry install
+```
+
+## Quick Start
+
+Generate a Git log in the required format:
+
+```bash
+cd your-project
+git log --all -M -C --numstat --date=short --pretty=format:'--%h--%cd--%cn' > git.log
+```
+
+Run a coupling analysis to find files that frequently change together:
+
+```bash
+code-maat coupling git.log --min-coupling 50 --rows 10
+# Or: python -m code_maat_python coupling git.log --min-coupling 50 --rows 10
+```
+
+Example output:
+```csv
+entity,coupled,degree,average-revs
+src/models/user.py,src/views/profile.py,87,45
+src/api/auth.py,src/middleware/session.py,76,32
+src/utils/validators.py,src/forms/registration.py,65,28
+```
+
+This indicates `user.py` and `profile.py` change together in 87% of commits where either file changes, based on 45 average revisions. High coupling may indicate shared responsibilities or implicit dependencies worth reviewing.
+
+## Available Analyses
+
+code-maat provides 17 analysis types:
+
+| Command | Description | Use Case |
+|---------|-------------|----------|
+| `coupling` | Temporal coupling between file pairs | Identify files that frequently change together |
+| `soc` | Sum of coupling scores per entity | Aggregate coupling metric for prioritization |
+| `entity-churn` | Lines added/deleted per entity over time | Measure change volatility |
+| `age` | Time since last modification | Identify stable or abandoned code |
+| `communication` | Shared code changes between authors | Map coordination requirements |
+| `authors` | Number of distinct authors per entity | Measure knowledge distribution |
+| `entity-ownership` | Line contribution percentage by author | Determine primary code owners |
+| `main-dev` | Primary contributor by lines changed | Identify domain experts |
+| `main-dev-by-revs` | Primary contributor by commit count | Identify active maintainers |
+| `refactoring-main-dev` | Primary contributor to refactorings | Track code quality effort |
+| `revisions` | Commit count per entity | Find frequently modified files |
+| `abs-churn` | Aggregate churn over time windows | Track development activity trends |
+| `author-churn` | Per-author contribution over time | Analyze individual contribution patterns |
+| `entity-effort` | Commit count per entity | Quantify development effort distribution |
+| `fragmentation` | Author distribution per entity | Detect coordination overhead |
+| `summary` | Repository-wide statistics | Overview metrics |
+| `entities` | List of all tracked entities | Verify log parsing scope |
+
+See [REFERENCE.md](REFERENCE.md) for detailed command documentation.
+
+## Documentation
+
+- [Setup Guide](docs/SETUP.md) — Git log format, shell aliases, advanced options
+- [Use Cases & Best Practices](docs/USE_CASES.md) — Application scenarios and analysis patterns
+- [Command Reference](REFERENCE.md) — Complete command documentation
+- [FAQ](docs/FAQ.md) — Common questions and further reading
+- [Contributing](CONTRIBUTING.md) — Contribution guidelines
+
+## License
+
+GPL-3.0 — see [LICENSE](LICENSE) for details.
+
+This project is inspired by and compatible with [Code Maat](https://github.com/adamtornhill/code-maat) by Adam Tornhill.
+

code_maat_python-0.2.0/README.md

@@ -0,0 +1,106 @@
+# code-maat
+
+[![License: GPL-3.0](https://img.shields.io/badge/License-GPL%203.0-blue.svg)](https://opensource.org/licenses/GPL-3.0)
+[![Python: 3.10+](https://img.shields.io/badge/python-3.10+-blue.svg)](https://www.python.org/downloads/)
+
+A Python implementation of [Code Maat](https://github.com/adamtornhill/code-maat) by Adam Tornhill. Analyzes Git repository history to identify code coupling, change patterns, and team dynamics.
+
+## Overview
+
+code-maat extracts insights from version control history:
+
+- Temporal coupling: Files that change together frequently
+- Code churn: Change frequency and stability metrics
+- Knowledge distribution: Contributor patterns and code ownership
+- Team coordination: Communication needs inferred from code changes
+
+These analyses help identify architectural dependencies not visible in static code structure, inform code review priorities, and understand how teams interact with code over time.
+
+## Why Use This Tool?
+
+Version control history contains information about code dependencies that aren't captured by static analysis. Files that frequently change together often share hidden coupling through business logic, data structures, or implicit contracts, even when they don't import each other directly.
+
+Research shows that files with high temporal coupling have 2-10x higher defect rates ([Predicting Faults from Cached History, MSR 2008](https://dl.acm.org/doi/10.1145/1453101.1453106)). Understanding these patterns helps with:
+
+- Prioritizing code review effort on coupled changes
+- Identifying coordination requirements between team members
+- Finding knowledge silos and ownership concentration
+- Discovering stable versus volatile areas of the codebase
+
+## Installation
+
+```bash
+# Using pip
+pip install code-maat
+
+# From source with Poetry
+git clone https://github.com/hydrosquall/code-maat.git
+cd code-maat
+poetry install
+```
+
+## Quick Start
+
+Generate a Git log in the required format:
+
+```bash
+cd your-project
+git log --all -M -C --numstat --date=short --pretty=format:'--%h--%cd--%cn' > git.log
+```
+
+Run a coupling analysis to find files that frequently change together:
+
+```bash
+code-maat coupling git.log --min-coupling 50 --rows 10
+# Or: python -m code_maat_python coupling git.log --min-coupling 50 --rows 10
+```
+
+Example output:
+```csv
+entity,coupled,degree,average-revs
+src/models/user.py,src/views/profile.py,87,45
+src/api/auth.py,src/middleware/session.py,76,32
+src/utils/validators.py,src/forms/registration.py,65,28
+```
+
+This indicates `user.py` and `profile.py` change together in 87% of commits where either file changes, based on 45 average revisions. High coupling may indicate shared responsibilities or implicit dependencies worth reviewing.
+
+## Available Analyses
+
+code-maat provides 17 analysis types:
+
+| Command | Description | Use Case |
+|---------|-------------|----------|
+| `coupling` | Temporal coupling between file pairs | Identify files that frequently change together |
+| `soc` | Sum of coupling scores per entity | Aggregate coupling metric for prioritization |
+| `entity-churn` | Lines added/deleted per entity over time | Measure change volatility |
+| `age` | Time since last modification | Identify stable or abandoned code |
+| `communication` | Shared code changes between authors | Map coordination requirements |
+| `authors` | Number of distinct authors per entity | Measure knowledge distribution |
+| `entity-ownership` | Line contribution percentage by author | Determine primary code owners |
+| `main-dev` | Primary contributor by lines changed | Identify domain experts |
+| `main-dev-by-revs` | Primary contributor by commit count | Identify active maintainers |
+| `refactoring-main-dev` | Primary contributor to refactorings | Track code quality effort |
+| `revisions` | Commit count per entity | Find frequently modified files |
+| `abs-churn` | Aggregate churn over time windows | Track development activity trends |
+| `author-churn` | Per-author contribution over time | Analyze individual contribution patterns |
+| `entity-effort` | Commit count per entity | Quantify development effort distribution |
+| `fragmentation` | Author distribution per entity | Detect coordination overhead |
+| `summary` | Repository-wide statistics | Overview metrics |
+| `entities` | List of all tracked entities | Verify log parsing scope |
+
+See [REFERENCE.md](REFERENCE.md) for detailed command documentation.
+
+## Documentation
+
+- [Setup Guide](docs/SETUP.md) — Git log format, shell aliases, advanced options
+- [Use Cases & Best Practices](docs/USE_CASES.md) — Application scenarios and analysis patterns
+- [Command Reference](REFERENCE.md) — Complete command documentation
+- [FAQ](docs/FAQ.md) — Common questions and further reading
+- [Contributing](CONTRIBUTING.md) — Contribution guidelines
+
+## License
+
+GPL-3.0 — see [LICENSE](LICENSE) for details.
+
+This project is inspired by and compatible with [Code Maat](https://github.com/adamtornhill/code-maat) by Adam Tornhill.

{code_maat_python-0.1.0 → code_maat_python-0.2.0}/code_maat_python/__init__.py

@@ -1,10 +1,10 @@
 """
-code-maat-python: Modern Python tool for mining VCS data with pandas.
+code-maat: Modern Python tool for mining VCS data with pandas.
 
 A rewrite of Code Maat (by Adam Tornhill) using pandas for data analysis.
 """
 
-__version__ = "0.1.0"
+__version__ = "0.2.0"
 __author__ = "Cameron Yick"
 __license__ = "GPL-3.0"
 

code_maat_python-0.2.0/code_maat_python/__main__.py

@@ -0,0 +1,5 @@
+"""Allow running code-maat as a module with python -m code_maat_python"""
+from code_maat_python.cli import main
+
+if __name__ == "__main__":
+    main()

{code_maat_python-0.1.0 → code_maat_python-0.2.0}/code_maat_python/analyses/__init__.py

@@ -1,4 +1,4 @@
-"""Analysis modules for code-maat-python."""
+"""Analysis modules for code-maat."""
 
 from code_maat_python.analyses.authors import analyze_authors
 from code_maat_python.analyses.churn import (

{code_maat_python-0.1.0 → code_maat_python-0.2.0}/code_maat_python/analyses/age.py

@@ -1,4 +1,4 @@
-"""Code age analysis for code-maat-python."""
+"""Code age analysis for code-maat."""
 
 import pandas as pd
 

{code_maat_python-0.1.0 → code_maat_python-0.2.0}/code_maat_python/analyses/authors.py

@@ -1,4 +1,4 @@
-"""Author analysis for code-maat-python.
+"""Author analysis for code-maat.
 
 Analyzes distinct authors per entity with revision counts.
 """

{code_maat_python-0.1.0 → code_maat_python-0.2.0}/code_maat_python/analyses/churn.py

@@ -1,4 +1,4 @@
-"""Churn analysis for code-maat-python.
+"""Churn analysis for code-maat.
 
 Analyzes code churn metrics including lines added/deleted by date, author,
 and entity, as well as main developer identification.

{code_maat_python-0.1.0 → code_maat_python-0.2.0}/code_maat_python/analyses/communication.py

@@ -1,4 +1,4 @@
-"""Communication analysis for code-maat-python."""
+"""Communication analysis for code-maat."""
 
 from itertools import combinations
 

{code_maat_python-0.1.0 → code_maat_python-0.2.0}/code_maat_python/analyses/coupling.py

@@ -1,4 +1,4 @@
-"""Logical coupling analysis for code-maat-python.
+"""Logical coupling analysis for code-maat.
 
 Calculate logical coupling between files based on co-change frequency.
 """

{code_maat_python-0.1.0 → code_maat_python-0.2.0}/code_maat_python/analyses/effort.py

@@ -1,4 +1,4 @@
-"""Effort analysis for code-maat-python.
+"""Effort analysis for code-maat.
 
 Analyzes author contributions by revision count and calculates
 code fragmentation metrics.

{code_maat_python-0.1.0 → code_maat_python-0.2.0}/code_maat_python/analyses/entities.py

@@ -1,4 +1,4 @@
-"""Entity listing analysis for code-maat-python.
+"""Entity listing analysis for code-maat.
 
 Lists all entities with basic statistics.
 """

{code_maat_python-0.1.0 → code_maat_python-0.2.0}/code_maat_python/analyses/revisions.py

@@ -1,4 +1,4 @@
-"""Revision frequency analysis for code-maat-python.
+"""Revision frequency analysis for code-maat.
 
 Analyzes and sorts entities by their revision frequency.
 """

{code_maat_python-0.1.0 → code_maat_python-0.2.0}/code_maat_python/analyses/soc.py

@@ -1,4 +1,4 @@
-"""Sum of Coupling (SOC) analysis for code-maat-python.
+"""Sum of Coupling (SOC) analysis for code-maat.
 
 Calculate sum of coupling for each entity based on commit size.
 """

{code_maat_python-0.1.0 → code_maat_python-0.2.0}/code_maat_python/analyses/summary.py

@@ -1,4 +1,4 @@
-"""Summary statistics analysis for code-maat-python.
+"""Summary statistics analysis for code-maat.
 
 Provides overview statistics for a repository.
 """

{code_maat_python-0.1.0 → code_maat_python-0.2.0}/code_maat_python/cli.py

@@ -1,4 +1,4 @@
-"""Command-line interface for code-maat-python.
+"""Command-line interface for code-maat.
 
 Modern CLI using click framework with subcommands for each analysis type.
 """
@@ -12,6 +12,7 @@ from typing import Any
 import click
 import pandas as pd
 
+from code_maat_python import __version__
 from code_maat_python.analyses import (
     analyze_authors,
     analyze_coupling,
@@ -179,9 +180,9 @@ def handle_analysis_error(e: Exception) -> None:
 
 # Main command group
 @click.group()
-@click.version_option(version="0.1.0", prog_name="code-maat-python")
+@click.version_option(version=__version__, prog_name="code-maat")
 def main() -> None:
-    """Code Maat Pandas - Modern Python tool for mining version control data.
+    """Code Maat - Modern Python tool for mining version control data.
 
     Analyzes git repository logs to identify patterns, coupling, churn,
     and other metrics useful for understanding code evolution.
@@ -193,10 +194,10 @@ def main() -> None:
                --pretty=format:'--%h--%cd--%cn' > git.log
 
         2. Run an analysis:
-           code-maat-python coupling git.log --min-coupling 50
+           code-maat coupling git.log --min-coupling 50
 
         3. Save results to CSV:
-           code-maat-python revisions git.log --output results.csv
+           code-maat revisions git.log --output results.csv
     """
     pass
 
@@ -218,9 +219,9 @@ def authors(
 
     \b
     Example:
-        code-maat-python authors git.log
-        code-maat-python authors git.log --output authors.csv
-        code-maat-python authors git.log --group layers.txt --rows 20
+        code-maat authors git.log
+        code-maat authors git.log --output authors.csv
+        code-maat authors git.log --group layers.txt --rows 20
     """
     try:
         df = parse_git_log(logfile)
@@ -248,9 +249,9 @@ def revisions(
 
     \b
     Example:
-        code-maat-python revisions git.log
-        code-maat-python revisions git.log --output revisions.csv
-        code-maat-python revisions git.log --group layers.txt --rows 10
+        code-maat revisions git.log
+        code-maat revisions git.log --output revisions.csv
+        code-maat revisions git.log --group layers.txt --rows 10
     """
     try:
         df = parse_git_log(logfile)
@@ -278,9 +279,9 @@ def entities(
 
     \b
     Example:
-        code-maat-python entities git.log
-        code-maat-python entities git.log --output entities.csv
-        code-maat-python entities git.log --group layers.txt
+        code-maat entities git.log
+        code-maat entities git.log --output entities.csv
+        code-maat entities git.log --group layers.txt
     """
     try:
         df = parse_git_log(logfile)
@@ -308,9 +309,9 @@ def summary(
 
     \b
     Example:
-        code-maat-python summary git.log
-        code-maat-python summary git.log --output summary.csv
-        code-maat-python summary git.log --group layers.txt
+        code-maat summary git.log
+        code-maat summary git.log --output summary.csv
+        code-maat summary git.log --group layers.txt
     """
     try:
         df = parse_git_log(logfile)
@@ -384,11 +385,11 @@ def coupling(
 
     \b
     Example:
-        code-maat-python coupling git.log
-        code-maat-python coupling git.log --min-coupling 50
-        code-maat-python coupling git.log --min-revs 10 --min-shared-revs 5
-        code-maat-python coupling git.log --group layers.txt --rows 20
-        code-maat-python coupling git.log --output coupling.csv
+        code-maat coupling git.log
+        code-maat coupling git.log --min-coupling 50
+        code-maat coupling git.log --min-revs 10 --min-shared-revs 5
+        code-maat coupling git.log --group layers.txt --rows 20
+        code-maat coupling git.log --output coupling.csv
     """
     try:
         # Validate parameters
@@ -442,10 +443,10 @@ def soc(
 
     \b
     Example:
-        code-maat-python soc git.log
-        code-maat-python soc git.log --max-changeset-size 50
-        code-maat-python soc git.log --group layers.txt --rows 10
-        code-maat-python soc git.log --output soc.csv
+        code-maat soc git.log
+        code-maat soc git.log --max-changeset-size 50
+        code-maat soc git.log --group layers.txt --rows 10
+        code-maat soc git.log --output soc.csv
     """
     try:
         df = parse_git_log(logfile)
@@ -473,9 +474,9 @@ def abs_churn_cmd(
 
     \b
     Example:
-        code-maat-python abs-churn git.log
-        code-maat-python abs-churn git.log --output churn.csv
-        code-maat-python abs-churn git.log --rows 30
+        code-maat abs-churn git.log
+        code-maat abs-churn git.log --output churn.csv
+        code-maat abs-churn git.log --rows 30
     """
     try:
         df = parse_git_log(logfile)
@@ -503,9 +504,9 @@ def author_churn_cmd(
 
     \b
     Example:
-        code-maat-python author-churn git.log
-        code-maat-python author-churn git.log --team-map-file teams.csv
-        code-maat-python author-churn git.log --output author-churn.csv
+        code-maat author-churn git.log
+        code-maat author-churn git.log --team-map-file teams.csv
+        code-maat author-churn git.log --output author-churn.csv
     """
     try:
         df = parse_git_log(logfile)
@@ -533,9 +534,9 @@ def entity_churn_cmd(
 
     \b
     Example:
-        code-maat-python entity-churn git.log
-        code-maat-python entity-churn git.log --group layers.txt --rows 20
-        code-maat-python entity-churn git.log --output entity-churn.csv
+        code-maat entity-churn git.log
+        code-maat entity-churn git.log --group layers.txt --rows 20
+        code-maat entity-churn git.log --output entity-churn.csv
     """
     try:
         df = parse_git_log(logfile)
@@ -563,9 +564,9 @@ def entity_ownership_cmd(
 
     \b
     Example:
-        code-maat-python entity-ownership git.log
-        code-maat-python entity-ownership git.log --group layers.txt
-        code-maat-python entity-ownership git.log --output ownership.csv
+        code-maat entity-ownership git.log
+        code-maat entity-ownership git.log --group layers.txt
+        code-maat entity-ownership git.log --output ownership.csv
     """
     try:
         df = parse_git_log(logfile)
@@ -593,9 +594,9 @@ def main_dev_cmd(
 
     \b
     Example:
-        code-maat-python main-dev git.log
-        code-maat-python main-dev git.log --group layers.txt --rows 15
-        code-maat-python main-dev git.log --output main-dev.csv
+        code-maat main-dev git.log
+        code-maat main-dev git.log --group layers.txt --rows 15
+        code-maat main-dev git.log --output main-dev.csv
     """
     try:
         df = parse_git_log(logfile)
@@ -623,9 +624,9 @@ def refactoring_main_dev_cmd(
 
     \b
     Example:
-        code-maat-python refactoring-main-dev git.log
-        code-maat-python refactoring-main-dev git.log --rows 10
-        code-maat-python refactoring-main-dev git.log --output refactoring.csv
+        code-maat refactoring-main-dev git.log
+        code-maat refactoring-main-dev git.log --rows 10
+        code-maat refactoring-main-dev git.log --output refactoring.csv
     """
     try:
         df = parse_git_log(logfile)
@@ -653,9 +654,9 @@ def entity_effort_cmd(
 
     \b
     Example:
-        code-maat-python entity-effort git.log
-        code-maat-python entity-effort git.log --group layers.txt
-        code-maat-python entity-effort git.log --output effort.csv
+        code-maat entity-effort git.log
+        code-maat entity-effort git.log --group layers.txt
+        code-maat entity-effort git.log --output effort.csv
     """
     try:
         df = parse_git_log(logfile)
@@ -683,9 +684,9 @@ def main_dev_by_revs_cmd(
 
     \b
     Example:
-        code-maat-python main-dev-by-revs git.log
-        code-maat-python main-dev-by-revs git.log --rows 15
-        code-maat-python main-dev-by-revs git.log --output main-dev-revs.csv
+        code-maat main-dev-by-revs git.log
+        code-maat main-dev-by-revs git.log --rows 15
+        code-maat main-dev-by-revs git.log --output main-dev-revs.csv
     """
     try:
         df = parse_git_log(logfile)
@@ -713,9 +714,9 @@ def fragmentation_cmd(
 
     \b
     Example:
-        code-maat-python fragmentation git.log
-        code-maat-python fragmentation git.log --group layers.txt --rows 20
-        code-maat-python fragmentation git.log --output fragmentation.csv
+        code-maat fragmentation git.log
+        code-maat fragmentation git.log --group layers.txt --rows 20
+        code-maat fragmentation git.log --output fragmentation.csv
     """
     try:
         df = parse_git_log(logfile)
@@ -750,10 +751,10 @@ def age(
 
     \b
     Example:
-        code-maat-python age git.log
-        code-maat-python age git.log --reference-date 2023-12-31
-        code-maat-python age git.log --group layers.txt --rows 25
-        code-maat-python age git.log --output age.csv
+        code-maat age git.log
+        code-maat age git.log --reference-date 2023-12-31
+        code-maat age git.log --group layers.txt --rows 25
+        code-maat age git.log --output age.csv
     """
     try:
         df = parse_git_log(logfile)
@@ -804,10 +805,10 @@ def communication_cmd(
 
     \b
     Example:
-        code-maat-python communication git.log
-        code-maat-python communication git.log --min-shared 10 --min-coupling 50
-        code-maat-python communication git.log --team-map-file teams.csv --rows 15
-        code-maat-python communication git.log --output communication.csv
+        code-maat communication git.log
+        code-maat communication git.log --min-shared 10 --min-coupling 50
+        code-maat communication git.log --team-map-file teams.csv --rows 15
+        code-maat communication git.log --output communication.csv
     """
     try:
         df = parse_git_log(logfile)

{code_maat_python-0.1.0 → code_maat_python-0.2.0}/code_maat_python/parser.py

@@ -1,4 +1,4 @@
-"""Git log parser for code-maat-python.
+"""Git log parser for code-maat.
 
 Parses git log output into pandas DataFrames for analysis.
 """

{code_maat_python-0.1.0 → code_maat_python-0.2.0}/code_maat_python/pipeline.py

@@ -1,4 +1,4 @@
-"""Data pipeline utilities for code-maat-python.
+"""Data pipeline utilities for code-maat.
 
 Provides utilities for transforming and filtering DataFrames between
 parsing and analysis stages.

{code_maat_python-0.1.0 → code_maat_python-0.2.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "code-maat-python"
-version = "0.1.0"
+version = "0.2.0"
 description = "Modern Python tool for mining and analyzing version control system data"
 authors = ["Cameron Yick <cameron.yick@gmail.com>"]
 license = "GPL-3.0"
@@ -34,7 +34,7 @@ pre-commit = "^3.3.0"
 pandas-stubs = "^2.0.0"
 
 [tool.poetry.scripts]
-code-maat-python = "code_maat_python.cli:main"
+code-maat = "code_maat_python.cli:main"
 
 [build-system]
 requires = ["poetry-core"]