Context
The problem
Engineering leads often don't know what's actually running across their repos, or which choices will hurt later.
Approach
How I built it
Scans a repository and builds a picture of its tech stack and the risks in it.
Checks the code against the team's rules and shows exactly where they're broken.
Writes a short summary of the architecture that non-engineers can read.
Result
What came out of it
Your stack at a glance
Rule checks with proof
Summaries anyone can read