Problem with current license AGPL-3.0

[kozi]

Due to the license AGPL-3.0, I cannot use the module in software whose source code I cannot/do not want to publish. Is this intentional, or would publication under an alternative license (MIT) be possible?

[baumerdev]

The choice of AGPL-3.0 was intentional. I want to prevent this library from being used in commercial SaaS projects that profit from it without contributing back.

Since I don't know your specific application, here are two examples: If you use the library internally, for example in an online shop where it validates a customer's bank account during checkout, and you include it via npm install and only use the validation results, then there is no need to publish your source code (users aren't "interacting with [ibantools-germany] remotely through a computer network" §13 AGPLv3).

But if you offer a public API endpoint such as /validate-iban that accepts data and returns validation results, then at least that part of your API would need to comply with an AGPL-compatible license.