By the way, I would appreciate if you could update your blog post to better reflect the state of Gambit's module system. The modules you wrote for Gambit have maintest in their name, but not the Chibi modules. In fact if you take the exact same Chibi modules and execute gsi . main.scm you will get the same output as Chibi (which unfortunately includes . in its module search algorithm by default, a security issue similar to including . in your shell's PATH). One of the important goals of the R7RS effort was to have a library system that would be portable to multiple implementations of Scheme and for the most part it achieves this. Lets not take the small issues and blow them out of proportion.

You might want to use the link https://gambitscheme.org/4.9.4/manual/#Modules for those interested in the details of Gambit's module system.

Finally, I don't mind the "risky scheme" part in the title. Security is an important issue and automatic installation of modules from github.com/gambit raises valid security concerns for which I would like a discussion. The automatic installation feature is particularly useful for transparent code migration in a distributed system, and also to share modules of code transparently with trusted colleagues or simply from your own github/gitlab account.