It sounds simple: clone every repo, parse the files, build a graph. Here's why each ecosystem fights back, and what it actually takes to map cross-repo dependencies automatically.
In the last post, I wrote about the infrastructure dependency visibility gap. The fact that most platform teams have no way to answer "if I change this, what else breaks?" across their repos. The community response confirmed what I'd seen at every client: people are building brittle grep scripts, maintaining stale spreadsheets, or just relying on whoever has been around the longest.
The obvious next question is: why doesn't anyone just parse the repos and build a graph?
The answer is that people do. Multiple engineers I've spoken with have built their own versions; a nightly cron job, some shell scripts, a SQLite database. And those solutions work, for a while, for one org, for the file types they remembered to handle. Then they hit an edge case, go stale, or the person who built it moves on.
The core approach is right: scan every repo, parse the files that declare dependencies, resolve them to actual repos, build a directed graph. But the devil is in the details, and each ecosystem has its own set of devils. This post walks through what it actually takes to auto-discover cross-repo dependencies across Terraform, Docker, CI pipelines, Python, Go, npm, Ansible, Helm, and Kubernetes, and why the cross-ecosystem problem is harder than any individual one.
