Skip to main content


SourceSage

~Transforming code for AI~
PyPI - Version PyPI - Format PyPI - Implementation PyPI - Status PyPI - Downloads PyPI - Downloads

SourceSage - Sunwood-ai-labs GitHub Repo stars forks - Sunwood-ai-labs GitHub Last Commit GitHub Top Language GitHub Release GitHub Tag GitHub Actions Workflow Status

[🌐 Website] • [🐱 GitHub] [🐦 Twitter] • [🍀 Official Blog]

日本語 | English

SourceSage is a tool that comprehensively analyzes repository structure and content to generate AI-friendly documentation. It primarily provides Repository_summary.md generation and RELEASE_REPORT creation features.

[!IMPORTANT] Nearly 90% of the release notes, README, and commit messages in this repository are generated using AIRA, SourceSage, Gaiah, and HarmonAI_II with claude.ai and ChatGPT4.

SourceSage MCP Server

SourceSage MCP Server is a derived version of SourceSage that integrates with the Model Context Protocol (MCP). It enables AI assistants like Claude Desktop to directly access repository analysis capabilities.

Release Notes

For the latest updates, please visit our GitHub releases page.

https://github.com/Sunwood-ai-labs/SourceSage/releases

🎯 Key Features

SourceSage is a simple and lightweight repository analysis tool that provides two main features:

1. 📋 Repository Summary Generation

Comprehensively analyzes repository structure, commit information, and file statistics to generate AI-friendly markdown documentation.

Output File: .SourceSageAssets/Repository_summary.md

Included Information:

  • 🌳 Project tree structure
  • 📋 Git repository information
  • 📈 File size and line count statistics
  • 📝 Detailed file contents

2. 📄 Release Report Generation (Optional Feature - Deprecated)

⚠️ Deprecated Feature: This feature will be removed in a future release. With improvements in LLM command execution capabilities, automatic diff report generation is becoming unnecessary.

Analyzes differences between Git tags to automatically generate release reports (enabled with --diff flag).

Output File: .SourceSageAssets/RELEASE_REPORT/Report_{latest_tag}.md

Included Information:

  • 🏷️ Version comparison
  • 🔄 Detailed change differences
  • 📋 Commit history
    • 📂 Repository basic information (remote URL, branch, latest commit, etc.)
    • 📖 README content (optional)

🚀 Quick Start

📦 Installation (Fastest)

git clone https://github.com/Sunwood-ai-labs/SourceSage.git
cd SourceSage
uv sync
uv run sage

Note: When using as a package, run pip install sourcesage then execute sage (or sourcesage).

🗺️ Basic Usage (Minimum Required)

# Generate repository summary (default: uses .gitignore)
uv run sage

# Use/generate .SourceSageignore file
uv run sage --use-ignore

# Generate release report (optional - deprecated)
uv run sage --diff

Output locations:

  • Repository Summary: .SourceSageAssets/Repository_summary.md
  • Release Report: .SourceSageAssets/RELEASE_REPORT/Report_{latest_tag}.md (only with --diff)

Frequently used options (excerpt):

uv run sage -o ./out                     # Change output destination
uv run sage --ignore-file .gitignore     # Specify ignore rules (default)
uv run sage --use-ignore                 # Use/generate .SourceSageignore
uv run sage --diff                       # Generate diff report (deprecated)

Notes:

  • From v7.2.0, .gitignore is used by default. Use --use-ignore if you need a custom ignore file.
  • When --language-map is omitted, the included defaults (sourcesage/config/) are automatically used.
  • Release Report is generated when there are 2 or more tags (only with --diff).

🔄 Upgrade

# If installed via PyPI
pip install --upgrade sourcesage

# If installed via git clone
git pull origin main

# If using uv with local clone
uv sync

🔍 Troubleshooting

uvx cache issues

If uvx sourcesage is using an outdated version, clear the cache:

# Force refresh (recommended)
uvx --refresh sourcesage --repo tmp

# Clear all uv cache
uv cache clean

# Clear specific package cache
uv cache clean sourcesage

# Run without cache
uvx --no-cache sourcesage --repo tmp

Cache management

# Check cache size
uv cache size

# Show cache directory
uv cache dir

# Prune unused cache
uv cache prune

📊 Example Generated Content

Repository Summary

    # Project: SourceSage

    ```plaintext
    OS: posix
    Directory: /path/to/project

    ├── .SourceSageignore
    ├── pyproject.toml
    ├── sourcesage/
    │   ├── __init__.py
    │   ├── cli.py
    │   └── modules/
    │       ├── DocuSum/
    │       └── DiffReport/
    │           ├── __init__.py
    │           ├── git_diff.py
    │           └── markdown_report.py
    └── README.md
    ```

    ## 📊 Project Statistics

    - 📅 Created: 2025-02-02 16:22:31
    - 📁 Total directories: 5
    - 📄 Total files: 15
    - 📏 Max depth: 3

    ### 📊 File Size and Line Count

    | File | Size | Lines | Language |
    |------|------|-------|----------|
    | pyproject.toml | 1.2 KB | 30 | TOML |
    | **Total** |  | **1234** |  |

    ### 📈 Language Statistics

    | Language | Files | Total Lines | Total Size |
    |----------|-------|-------------|-----------|
    | Python | 15 | 1234 | 45.6 KB |
    | Markdown | 3 | 150 | 5.2 KB |

🛠️ Development Environment

SourceSage supports modern Python development environments:

  • Python: 3.8 or later
  • Package Management: uv / pip
  • Build System: hatchling
  • Configuration File: pyproject.toml

Development Setup

# Development environment setup using uv
git clone https://github.com/Sunwood-ai-labs/SourceSage.git
cd SourceSage
uv sync

# Run tests
uv run pytest

# Code formatting
uv run black sourcesage/
uv run isort sourcesage/

# Build package
uv build

💡 Usage Examples

# 1) Output repository summary (default: uses .gitignore)
uv run sage

# 2) Output summary using .SourceSageignore
uv run sage --use-ignore

# 3) Generate diff report (deprecated feature)
uv run sage --diff

# 4) Change output destination
uv run sage -o ./analysis

Contributing

Help us improve SourceSage! If you have bug reports or feature suggestions, please open an issue or submit a pull request at our GitHub repository.

License

This project is released under the MIT License.


Featured on Orynth

SSAGE (Solana mint): 1QaAfN81sYjenLGeiPa9NW1s6FND4A36R3ASKKxVory

Primary pool (SSAGE/USDC, Meteora): https://www.geckoterminal.com/solana/pools/A4oHVtJxGRRYvqfRuUGPwfxFVdBmPJnYZtcqew5Y8HoH

Dexscreener: https://dexscreener.com/solana/a4ohvtjxgrryvqfruugpwfxfvdbmpjnyztcqew5y8hoh

Note: SSAGE is a community market token/identifier for the SourceSage project on Orynth. It is not equity, ownership, or a claim on the project. No investment advice.

Metadata

Release files for sourcesage 7.2.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for sourcesage 7.2.2
File Size Uploaded
sourcesage-7.2.2.tar.gz 27.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for sourcesage 7.2.2
File Interpreter ABI Platform
sourcesage-7.2.2-py3-none-any.whl Python 3 none any Details

Total release size: 63.0 kB

Release files / sourcesage-7.2.2.tar.gz

Download URL sourcesage-7.2.2.tar.gz
Size 27.0 kB
Tags Source
SHA-256 checksum
How to use checksums
eae05865c091dff1f5a7320d780f6765479a8148f2a2fe3fb6c61193c34f1097
BLAKE2b-256 checksum
How to use checksums
cd8e2da67f82fba6bc93763669aca9d01f0854373f9950104343f8c6bcd7f680
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 21, 2026.

Transparency log

Release files / sourcesage-7.2.2-py3-none-any.whl

Download URL sourcesage-7.2.2-py3-none-any.whl
Size 36.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
97bf48daf549c835404e6e182fbd113e498add56521dc493fabd9c58193a4d02
BLAKE2b-256 checksum
How to use checksums
f838a46a1b280f169ddf9c4e19572b0dc55146e274ee9d54adf7595e5d812e29
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 21, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

7.2.2 This release

2 release files

7.1.1

2 release files

7.1.0

2 release files

7.0.1

2 release files

6.2.0

2 release files

6.1.1

2 release files

6.0.0

2 release files

5.6.1

2 release files

5.6.0

2 release files

5.5.1

2 release files

5.5.0

2 release files

5.4.0

2 release files

5.3.0

2 release files

5.2.1

2 release files

5.2.0

2 release files

5.1.1

2 release files

5.1.0

2 release files

5.0.2

2 release files

5.0.1

2 release files

5.0.0

2 release files

4.4.0

2 release files

4.3.0

2 release files

4.2.1

2 release files

4.2.0

2 release files

4.1.6

2 release files

4.1.5

2 release files

4.1.4

2 release files

4.1.2

2 release files

4.1.1

2 release files

4.0.9

2 release files

4.0.8

2 release files

4.0.7

2 release files

4.0.6

2 release files

4.0.5

2 release files

4.0.4

2 release files

4.0.3

2 release files

4.0.2

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page