{"id":47242815,"title":"Show HN: Atlas – Portfolio health dashboard for multi-repo teams (Python CLI)","points":1,"user":"vipdestiny","time":1772596099,"time_ago":"10 hours ago","type":"link","content":"

I manage 8+ mixed repos (prod, dev, poc) across Python, TypeScript, and Rust. Every dev tool I use -- Cursor, Copilot, Claude Code -- is great inside a single repo. But none of them answer the cross-cutting questions:

Which repos have zero tests?\n- Are my React versions consistent across 3 frontends?\n- Which project hasn't been committed to in weeks?\n- Where am I duplicating FastAPI patterns instead of sharing a library?

I got tired of manually checking, so I built Atlas. It's a Python CLI that scans your repos locally and gives you a portfolio-level health dashboard.

What it does\nPoint it at your projects, run atlas scan, and you get this:

  pip install nxtg-atlas\n\n  atlas init --name "My Portfolio"\n  atlas add ~/projects/api\n  atlas add ~/projects/frontend\n  atlas scan\n  atlas status\n

\nReal output from my 8 production repos:

+---------+--------------------+----------+--------+----------+---------------------+\n| | Project | Health | Tests | LOC | Tech Stack |\n+---------+--------------------+----------+--------+----------+---------------------+\n| (green) | Dx3 | A 94% | 179 | 164,806 | Python . TypeScript |\n| (green) | content-engine | B+ 88% | 23 | 12,552 | Python |\n| (green) | Podcast-Pipeline | B+ 88% | 49 | 33,680 | Python . FastAPI |\n| (green) | nxtg.ai | B+ 87% | 36 | 49,938 | TypeScript . Next.js|\n| (green) | Faultline | B+ 86% | 29 | 15,527 | TypeScript . React |\n| (green) | voice-jib-jab | B+ 86% | 58 | 45,311 | TypeScript . Python |\n| (yellow)| SynApps | C 67% | 114 | 793,406 | Python . TypeScript |\n| (red) | NXTG-Forge | D 59% | 121 | 136,083 | TypeScript . Rust |\n+---------+--------------------+----------+--------+----------+---------------------+

8 Projects | 609 Test Files | 1,251,303 LOC | Scanned in 31 seconds\nThat's not a mockup. That's the actual output from scanning our production portfolio. The C and D grades were embarrassing -- but that's the point. You can't fix what you can't see.

How health scoring works\nEach project gets an A-F grade based on 4 weighted dimensions:

- Tests (35%) -- test file count relative to source files\n - Structure (25%) -- CI/CD, .gitignore, package config, linting, source organization\n - Git Hygiene (20%) -- commit history, remote status, clean working tree\n - Documentation (20%) -- README, CHANGELOG, docs/, etc.

Cross-project intelligence\nThis is where it gets interesting. Atlas compares deps and versions across all your repos:

- Shared dependencies (fastapi used in 4 projects, react in 3)\n - Version mismatches (react ^18.2.0 in one app, ^19.2.1 in another)\n - Health gaps (3 projects with zero tests, 1 with 50+ uncommitted changes)\n - These are the things that bite you six months from now.

What it is NOT\n - Not a cloud service. Zero network calls, no telemetry, no accounts.\n - Not a linter or code quality tool. It doesn't read your source code line by line.\n - Not a replacement for SonarQube / CodeClimate. Those go deep on one repo. Atlas goes wide across many.

Details\n - Python 3.11+, built with Typer + Rich\n - State is a single JSON file at ~/.atlas/portfolio.json\n - Detects 10+ languages, 15+ frameworks, 5+ databases\n - MIT license, 100% open source — no tiers, no limits, no feature gates\n - Everything works: unlimited projects, cross-project intelligence, export, batch-add

--> GitHub: https://github.com/nxtg-ai/repoatlas\n--> PyPI: https://pypi.org/project/nxtg-atlas/

If atlas saves you time, consider supporting development.

Happy to answer questions about the scoring algorithm, the detection heuristics, or how we're using it internally.","url":"https://github.com/nxtg-ai/repoatlas","domain":"github.com","comments":[],"comments_count":0}