Project Info
This project did not submit a demo video on Devpost.
Inspiration
Having worked with large codebases before, we know how overwhelming it can be to navigate and understand them—both for humans and AI. We wanted to create a low-token representation of a codebase that preserves its structure while making it easier to explore. Our goal was to fundamentally change how developers view and interact with code by introducing a hierarchical, AI-powered interface that abstracts away complexity and allows users to drill down only when necessary. We were also inspired by tools like Windsurf, which we love, and wanted to bring that intuitive experience to AI-powered code analysis.
What it does
Rebase is an AI-powered code analytics tool that helps developers quickly understand large codebases. It features: A tree-based file explorer for intuitive navigation AI-generated summaries and complexity analysis for files Code analytics, including lines of code, commits, and files changed AI-powered visualizations and diagrams to represent code structure GitHub integration for real-time insights
How we built it
We focused on designing an intuitive hierarchical interface that enables users to interact with code at different levels of abstraction. Our backend processes code efficiently, generating AI-powered summaries, complexity scores, and visualizations. We also worked on GitHub authentication and integrating real-time analytics into the dashboard.
Challenges we ran into
One of the biggest challenges was handling GitHub authentication—we were stuck on it for a while. Managing dependencies across files efficiently and optimizing AI context window usage were also tricky. Balancing performance with usability was another key challenge, especially when working with large codebases.
Accomplishments we're proud of
Successfully built a working prototype of our file tree explorer Implemented AI-generated summaries and complexity analysis Designed a scalable approach for integrating GitHub repositories Gained a deeper understanding of AI-driven software engineering
What we learned
Throughout this project, we learned a lot about: AI-driven software engineering and code analysis Managing dependencies across files in a structured way Efficiently utilizing the context window for AI-powered insights Overcoming authentication and API integration hurdles
What's next
This is just the beginning. Moving forward, Rebase can expand to integrate with popular AI software engineering services, provide deeper insights into code structure, and support more advanced AI-driven refactoring suggestions. Our goal is to make navigating and understanding large codebases effortless for developers everywhere.
Analysis
View
Metric
- 9
- 8
- 3
Figures cover GitHub contributors during the hackathon window. A co-authored commit counts in full for each author, so per-member totals add up to more than the whole-team figures.
Technology
- CSSIn code
- FlaskIn code
- HTMLIn code
- JavaScriptIn code
- OpenAIIn code
- PythonIn code
- ReactIn code
- Tailwind CSSIn code
- PostgreSQLClaimed
8 of 9 appear in the indexed code. 1 claimed on Devpost could not be matched to code, which may simply mean the tool leaves no trace in the repository.
AI coding agents
No AI coding agent signals were found in this repository.
Detected from committed agent config files and commit authorship. Absence of a signal is not proof an agent was unused.
Codebase size
Source size
81 KB
Source files
25
Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.
Repository
evnkim/treehacks2025
32 files · 146 KB · @ 7c171ee
Structure
Interface
8 files · 25%Screens, components and styles rendered to the user.
API & routing
7 files · 22%Request entry points: routes, handlers and controllers.
Application logic
5 files · 16%Domain rules, services and shared utilities.
Data & schema
3 files · 9%Schema definitions, migrations and data access.
Supporting
Layers are inferred from where files sit in the tree, not from reading the code. A project that names its directories unconventionally will read oddly here — open the file browser to check anything the diagram implies.
Languages
- Python50%
- JavaScript49%
- HTML0%
- Markdown0%
- CSS0%
Share of indexed source by file size. Binary and vendored files are excluded.
Dependencies
client/package.json
npm · 20- @mantine/core
- @mantine/hooks
- @tabler/icons-react
- @tailwindcss/vite
- chart.js
- chartjs
- chartjs-adapter-date-fns
- chartjs-plugin-zoom
- date-fns
- icons-react
- react
- react-chartjs-2
- react-dom
- react-icons
- react-router-dom
- +5 more
requirements.txt
pypi · 11- APIFlask
- Authlib
- Faker
- Flask
- Flask-Cors
- Flask-SQLAlchemy
- openai
- psycopg2-binary
- python-dotenv
- requests
- SQLAlchemy
Declared in the repository’s manifests at the indexed commit. A declared package is not proof it is used, and runtime dependencies are listed first.
This project’s features have not been analysed yet.
Export this project's context (description, README, evidence, key source files) to chat with an AI agent elsewhere.