Disclaimer use restrictions not compatible with AGPL #145

New issue

Open

opened 2025-10-14 16:47:52 -06:00 by navan · 0 comments

navan commented

2025-10-14 16:47:52 -06:00

Owner

Originally created by @elliotwutingfeng on 12/5/2022

According to the GNU GPL FAQs page (which also applies to the AGPL), a license that limits who can use a program, or for what, is not a free software license.

Thus, this usage restriction statement "Use it only in personal, criminal investigations, pentesting, or open-source projects." in the readme is not compatible with the AGPL.

Though technically, every project that includes AGPL code has to be open-source anyway, but the original AGPL text already includes the "disclose source" requirement.

Solution

This can be resolved by removing the statement "Use it only in personal, criminal investigations, pentesting, or open-source projects." or alternatively by keeping the statement and using a non-free license similar to the AGPL that also allows for software usage restrictions.

*Originally created by @elliotwutingfeng on 12/5/2022* According to the GNU GPL FAQs [page](https://www.gnu.org/licenses/gpl-faq.html#NoMilitary) (which also applies to the AGPL), a license that limits who can use a program, or for what, is [not a free software license](https://www.gnu.org/philosophy/programs-must-not-limit-freedom-to-run.html). Thus, this usage restriction statement "Use it only in personal, criminal investigations, pentesting, or open-source projects." in the readme is not compatible with the AGPL. Though technically, every project that includes AGPL code has to be open-source anyway, but the original AGPL text already includes the "disclose source" requirement. **Solution** This can be resolved by removing the statement "Use it only in personal, criminal investigations, pentesting, or open-source projects." or alternatively by keeping the statement and using a non-free license similar to the AGPL that also allows for software usage restrictions.