I think the linking or way of inclusion is what matters, not way of distribution, since AGPL covers all conventional distrobution. With GPL, distribution is source code or complied code (binary or bytecode), with AGPL distribution access to running code over a network is covered on top of that.

I don't read AGPL that way. First, they do specify method of distribution

To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.

Second, there is this clause that could apply to SaaS if the module was modified:

Notwithstanding any other provision of this License, **if you modify the Program**, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge

@adam_roderick Both end up with, if someone can access it, they should be able to see the source. I think it’s the “A ‘covered work’ means either the unmodified Program or a work based on the Program.” So I think what ends up being debated is what constitutes “a work based on the Program”.