NOTICE: This project is still going to be updated over time but the hosted environment I've been hosting on my homelab is going to be down for some time just due to some reconfigurations I'm doing internally. Please still feel free to fork and run this for yourself!
Repository archaeology and static analysis platform.
Paste a GitHub repository URL and get deep architecture insights, commit history analysis, dependency health reports, security findings, OSS readiness scoring, and contributor guidance.
Atlas Insight performs deterministic repository analysis entirely within the application and can optionally generate structured context for use with external AI tools.
Atlas Insight does not send repository contents to AI providers. Optional export features generate structured context that users may manually provide to external AI tools.
Analysis results are archived. Re-running a repository first checks for new commits and reuses existing results when nothing has changed.
Quick Links: Features • Quick Start • API • Deployment • Wiki • Discussions • Discord • Contributing
Documentation & Community:
- Project Wiki: https://github.com/LunarVagabond/Atlas-Insight/wiki
- GitHub Discussions: https://github.com/LunarVagabond/Atlas-Insight/discussions
- Project policies and contribution rules: CONTRIBUTING.md, SECURITY.md, CODE_OF_CONDUCT.md, and LICENSE remain canonical in this repository.
- Discord: https://discord.gg/SG23W3BqCn — general tech community; drop in for Atlas Insight feedback, OSS discussion, or just to hang out
![]() |
![]() |
![]() |
![]() |
| Feature | What you get |
|---|---|
| Commit analysis | Velocity trends, contributor churn, burnout signals, activity decay |
| Architecture analysis | Import graphs, circular dependencies, god modules, hot files |
| Dependency health | Dependency inventory, lockfile checks, Docker image warnings |
| Security scanning | Secret detection, .gitignore hygiene, repository safety signals |
| Heuristic scoring | Repository risk and maintenance indicators with mode-aware weighting |
| Health score | Composite readiness assessment from 0–10 (OSS and closed-source modes) |
| Contributing path | Actionable contribution opportunities from issues and repository structure |
| Architecture tours | Guided exploration paths through major subsystems |
| Spotlight & Trending | Weekly featured repo and community discovery views |
| Health badges | Embeddable SVG badges for analyzed repositories |
OSS Score is a heuristic assessment of how approachable and maintainable a repository is for open-source contributors.
The score incorporates signals such as:
- Documentation quality
- Contributor friendliness
- Repository activity
- CI/CD maturity
- Dependency health
- Security hygiene
- Project structure
- Contributor distribution and bus factor
- Maintenance indicators
- Open issue management
- Development practices
OSS Score is intended as a directional indicator rather than an objective measure of software quality. A lower score may highlight maintenance or contribution risks rather than deficiencies in the software itself.
| Layer | Technology |
|---|---|
| Backend API | Django 5 + Django Ninja |
| Task Queue | Celery + Redis |
| Database | PostgreSQL 17 |
| Frontend | Vue 3 + TypeScript + Vite + Pinia |
Default Ports
| Service | Port |
|---|---|
| Django API | 4500 |
| Vite Dev Server | 4501 |
| Redis | 4502 |
| PostgreSQL | 4503 |
| Flower | 4504 |
cp backend/.env.example backend/.env
# Optional but recommended:
# Add a GITHUB_TOKEN for higher GitHub API rate limits
make setup
docker compose up -d
make -C backend migrate
make start| Service | URL |
|---|---|
| Frontend | http://localhost:4501 |
| API | http://localhost:4500 |
| OpenAPI Docs | http://localhost:4500/api/docs |
| Flower | http://localhost:4504 |
make start
make stop
make restart
make status
make logscd backend
# Run management commands
DJANGO_SETTINGS_MODULE=config.settings.development .venv/bin/python manage.py <command>
# Run tests
DJANGO_SETTINGS_MODULE=config.settings.development .venv/bin/pytest
# Run a specific test file
DJANGO_SETTINGS_MODULE=config.settings.development .venv/bin/pytest apps/repositories/tests/test_models.py
# Linting
.venv/bin/ruff check .
# Formatting
.venv/bin/black .cd frontend
# Type checking
node_modules/.bin/vue-tsc --noEmit
# Unit tests
npm test
# Production build
make buildmake test # backend pytest + frontend vitest
make lint # ruff + vue-tsc
make type-check # vue-tsc onlyInteractive OpenAPI documentation is available at:
/api/docs
when the application is running.
| Method | Endpoint | Description |
|---|---|---|
| POST | /api/v1/repositories/analyze |
Submit a repository for analysis |
| GET | /api/v1/repositories/runs/{id} |
Retrieve analysis status and results |
| GET | /api/v1/repositories/badge/{owner}/{name}.svg |
Generate repository health badge |
These endpoints retrieve live data and cache responses in Redis for 15 minutes unless otherwise noted.
| Method | Endpoint | Description |
|---|---|---|
| GET | /api/v1/repositories/runs/{id}/issues |
Live GitHub issues |
| GET | /api/v1/repositories/runs/{id}/prs |
Open pull requests |
| GET | /api/v1/repositories/runs/{id}/diff |
Delta from previous analysis |
| GET | /api/v1/repositories/runs/{id}/file-history?path=<path> |
Recent file history |
| GET | /api/v1/repositories/runs/{id}/similar |
Similar repository profiles |
| GET | /api/v1/repositories/runs/{id}/vulnerabilities |
Dependency vulnerability data |
| GET | /api/v1/repositories/runs/{id}/constellation |
Repository relationship graph |
| GET | /api/v1/repositories/runs/{id}/ai-summary |
AI-generated run summary |
| GET | /api/v1/repositories/runs/{id}/pr-impact?pr=<num> |
PR impact analysis |
| Method | Endpoint | Description |
|---|---|---|
| GET | /api/v1/repositories/spotlight/current |
Current Repo of the Week |
| GET | /api/v1/repositories/spotlight/history |
Past spotlight picks |
| GET | /api/v1/repositories/trending |
Trending public repositories |
| GET | /api/v1/repositories/featured |
Featured repository list |
| GET | /api/v1/health |
Service health check |
Production deployment documentation is available in the GitHub Wiki:
https://github.com/LunarVagabond/Atlas-Insight/wiki
The deployment guide includes:
- Nginx configuration
- systemd services
- Environment variables
- PostgreSQL setup
- Redis configuration
- Reverse proxy configuration
- Operational guidance
See Roadmap for the post-FOSS path and the longer-term product ideas we want to keep revisiting.
Atlas Insight welcomes contributors interested in repository structure, maintenance, and improvement. Django or Vue expertise is not required; many contributions begin with documentation updates or a new language parser scaffold.
| I want to… | Start here |
|---|---|
| Fix a bug | Open a bug report → CONTRIBUTING.md |
| Add a language parser | Project Wiki → make new-language |
| Add an infra tool detector | Project Wiki → make new-tool |
| Improve docs | Project Wiki |
| Explore bigger ideas | Roadmap (Wiki) |
- Follow CONTRIBUTING.md for setup, branch naming (
<issue>-<desc>ornoissue-<desc>), and PR title format. - Run
make testandmake lintfrom the repo root. - Review the Project Wiki for setup, project layout, and analysis pipeline guidance.
Also review SECURITY.md and CODE_OF_CONDUCT.md before submitting pull requests.
Not just an Atlas Insight server — a general tech community and hangout. Whether you want to give feedback on the project, talk OSS, or just connect with other developers, you're welcome.
- Give feedback on Atlas Insight
- Discuss OSS health, repo archaeology, and tooling
- Talk tech, ask questions, share projects
- Just hang out
Released under the MIT License.
See LICENSE for details.
If Atlas Insight has been useful and you want to support ongoing development, consider buying me a coffee.



