The dump opens up possibilities. That is great. I have gotten the beginnings of a reader but wondering fthere are example programs that display all the dependencies, or list all the compiler options already? One of the issues with creating more powerful plugins for fpm is access to the model from an external process which this dump and/or the --show-model switch look poised to solve, but it would be really useful to see some examples of converting the model back to fortran types. I am not normally a heavy JSON/TOML user having used my own file format and NAMELIST and hdf4/hdf5 before they became popular so I am probably making mistakes. Reading in the table and then getting all the filenames along with the module names they generate and the names of the modules used looks to be giving me the basics for creating *.o: dependency lines which should allow for generating basic interfaces for self-contained src/ directories. And include information is availble too, but so far things are not clear on what to do with dependencies. The primary function that makes fpm(1) attractive is replacing the need for make-like tools; but working with a repository and remove packages from source is beyond simple make usage (although makes’ simple interfacng with system commands makes it possible by calling wget, curl, git, … . fpm is very weak at leveraging other commands. That obviously has a good side but can be limiting.