About the Project

💡 Inspiration

Modern software projects can become difficult to maintain even when the application itself appears to work. Important engineering signals such as missing documentation, absent tests, unmanaged dependencies, missing CI workflows, and accidentally committed secret files can easily be overlooked.

We wanted to create a simple developer tool that could provide a quick health check of a repository instead of requiring developers to inspect these areas manually.

That idea led to RepoPilot — Repository Health Assistant.

🚀 What We Built

RepoPilot analyzes a repository and converts common software-engineering signals into an easy-to-understand health report.

The workflow is:

Repository ZIP → Static Analysis → Engineering Signals → Health Score → Findings → Recommendations → Report

RepoPilot currently checks:

  • Repository structure
  • Programming languages
  • README/documentation presence
  • Dependency manifests
  • Test files
  • GitHub Actions / CI configuration
  • Potential secret files
  • Source-code size signals

The tool then calculates a repository health score and explains the detected issues with actionable recommendations.

🛠️ How We Built It

We built RepoPilot using Python and Streamlit.

Python handles the repository analysis using filesystem and archive-processing utilities. The analyzer identifies engineering signals using deterministic and explainable rules rather than making unsupported assumptions about the code.

Streamlit provides the interactive interface where users can upload a repository ZIP, start an analysis, view the results, and download a Markdown health report.

The project follows a simple architecture:

Repository ZIP
      ↓
Secure ZIP Extraction
      ↓
Repository Scanner
      ↓
Engineering Signal Detection
      ↓
Health Score Calculation
      ↓
Findings & Recommendations
      ↓
Interactive Dashboard
      ↓
Markdown Health Report

Built With

Share this project:

Updates

Submission history