Why dependency impact is more than search

Changing a shared package is easy. Knowing where that change lands is harder.

In a multi-repository setup, direct manifest search only answers the first layer of the question. Consumers may reach a package through another internal library, or the only reliable evidence may live in a lockfile. Dependency Radar started from a practical need: make those paths visible before publishing, without requiring a monorepo migration.

This is the first build note. Future posts will cover graph traversal limits, ambiguous package versions, and the differences between npm, Yarn, and pnpm lockfiles.