# Dependency visualization tool

**URL:** <https://discuss.ocaml.org/t/dependency-visualization-tool/7964>\
**Category:** Ecosystem\
**Tags:** dependencies, opam\
**Created:** [June 4, 2021, 11:35am UTC](https://discuss.ocaml.org/t/dependency-visualization-tool/7964 "2021-06-04T11:35:51Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Chet\_Murthy](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/chet_murthy/32/1501_2.png) [@Chet\_Murthy](https://discuss.ocaml.org/u/Chet_Murthy)\
**Post date:** [June 8, 2021, 8:02pm UTC](https://discuss.ocaml.org/t/dependency-visualization-tool/7964/2 "2021-06-08T20:02:32Z")

</div>

In the past, I’ve found doing this sort of dependency-graphing to be very useful for figuring out where modularization in a large system needs to be applied. And it’s not very hard to do, based on ocamldep output or other dependency information that already exists.

On a lark, I wrote something that did this for installed findlib packages:

> **[chetmurthy/not-ocamlfind](https://github.com/chetmurthy/not-ocamlfind#package-graph)**
>
> front-end to ocamlfind (from findlib) to add a few new commands - chetmurthy/not-ocamlfind

I mention this not to plug the tool, but rather, just to note that it’s really easy, and yeah, people should avail themselves of this more.

---

_[View the full topic](https://discuss.ocaml.org/t/dependency-visualization-tool/7964)._