I think AGPL is probably your best bet if there is a chance a competitor will extend your code and release it as a SAAS. But also, the git repo has LICENSE wit

I think AGPL is probably your best bet if there is a chance a competitor will extend your code and release it as a SAAS. But also, the git repo has LICENSE with the AGPL, as well as LICENSE2 which just has some names followed by all rights reserved. It's a bit confusing, if there is dual licensing or some of the files are licensed differently maybe you should explain that in the LICENSE file, even if it means referencing a separate AGPL file. In any case it looks pretty neat, I think I'll give it a try.