Sourcetrail can still help explore code relationships, but its original repository is archived. That changes the risk calculation for new projects, especially when language servers and compiler versions keep moving.
Index a representative repository and follow a symbol from definition to callers and back. Test cross-language navigation, indexing time, ignored generated code, and the effect of a renamed symbol. Compare this with your IDE's built-in references or a maintained code explorer. The archived upstream repository is useful context when checking forks or current packages.
If Sourcetrail solves a unique navigation problem, document the pinned build and a way to reconstruct its index. Avoid depending on unsupported integrations without an owner. A useful tool should improve understanding today without creating a maintenance dead end tomorrow.
Akousa