Create a gist now

Instantly share code, notes, and snippets.

What would you like to do?
WPScan Public Source License
WPScan Public Source License
The WPScan software (henceforth referred to simply as "WPScan") is dual-licensed - Copyright 2011-2015 WPScan Team.
Cases that include commercialization of WPScan require a commercial, non-free license. Otherwise, WPScan can be used without charge under the terms set out below.
Definitions
“License” means this document.
“Contributor” means each individual or legal entity that creates, contributes to the creation of, or owns WPScan.
“WPScan Team” means WPScan’s core developers, an updated list of whom can be found within the CREDITS file.
Commercialization
A commercial use is one intended for commercial advantage or monetary compensation.
Example cases of commercialization are:
Using WPScan to provide commercial managed/Software-as-a-Service services.
Distributing WPScan as a commercial product or as part of one.
Using WPScan as a value added service/product.
Example cases which do not require a commercial license, and thus fall under the terms set out below, include (but are not limited to):
Penetration testers (or penetration testing organizations) using WPScan as part of their assessment toolkit.
Penetration Testing Linux Distributions including but not limited to Kali Linux, SamuraiWTF, BackBox Linux.
Using WPScan to test your own systems.
Any non-commercial use of WPScan.
If you need to purchase a commercial license or are unsure whether you need to purchase a commercial license contact us - wpscanteam@gmail.com.
We may grant commercial licenses at no monetary cost at our own discretion if the commercial usage is deemed by the WPScan Team to significantly benefit WPScan.
Free-use Terms and Conditions;
Redistribution
Redistribution is permitted under the following conditions:
- Unmodified License is provided with WPScan.
- Unmodified Copyright notices are provided with WPScan.
- Does not conflict with the commercialization clause.
Copying
Copying is permitted so long as it does not conflict with the Redistribution clause.
Modification
Modification is permitted so long as it does not conflict with the Redistribution clause.
Contributions
Any Contributions assume the Contributor grants the WPScan Team the unlimited, non-exclusive right to reuse, modify and relicense the Contributor's content.
Support
WPScan is provided under an AS-IS basis and without any support, updates or maintenance. Support, updates and maintenance may be given according to the sole discretion of the WPScan Team.
Disclaimer of Warranty
WPScan is provided under this License on an “as is” basis, without warranty of any kind, either expressed, implied, or statutory, including, without limitation, warranties that the WPScan is free of defects, merchantable, fit for a particular purpose or non-infringing.
Limitation of Liability
To the extent permitted under Law, WPScan is provided under an AS-IS basis. The WPScan Team shall never, and without any limit, be liable for any damage, cost, expense or any other payment incurred as a result of WPScan's actions, failure, bugs and/or any other interaction between WPScan and end-equipment, computers, other software or any 3rd party, end-equipment, computer or services.
Disclaimer
Running WPScan against websites without prior mutual consent may be illegal in your country. The WPScan Team accept no liability and are not responsible for any misuse or damage caused by WPScan.

Hi Ryan,
Recently I've read both sides of the history with delve labs and I want to say that I'm just a normal user meaning that I only use this awesome open project to harden my sites I know that you have put many effort in this project and I'm with you always that the normal usage won't be limited to things, the other thing that I was wondering is about all the contributions of the community you have permission from all these contributors to change the license? or you don't need it .

Thanks in advanced and regards.
Hector J.

droope commented Aug 16, 2015

Why not AGPL? http://www.affero.org/oagf.html

seems well suited for your use case?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment