Project Leader Name
What is your email address?
What is the Name of the Project
What is your project website address?
What category does your project fall under?
Library Project
Documentation Project
Tool Project
Which open source license does your project use?
Apache 2.0 License (fewest restrictions, even allowing proprietary modifications and proprietary forks of your project)
Creative Commons Attribution ShareAlike 3.0 License (best for documentation projects)
GNU GPL v3 License (allows commercial use, but requires that modifications to your code stay open source, thus prohibiting proprietary forks of your project)
GNU AGPL v3 License (similar to GPL but modified for use with web applications and web interfaces)
GNU LGPL v3 License (similar to GPL but modified for use with libraries that may be called by other proprietary programs)
Modified BSD, 3-clause License (we recommend you consider Apache 2.0 instead of this licnese. It is more up-to-date and provides a little more protection from software patent lawsuits)
other
The core principle of OWASP is openness. As a result, all projects MUST utilize an open source license. While we do not mandate any particular license, the overwhelming majority of projects at OWASP have chosen one of the licenses below. Please remember, our notes and recommendations should not be taken as legal advice.
Do you have an OWASP reviewed stable deliverable?
Yes
No
What is the name of your OWASP reviewed stable deliverable?
What you hope to accomplish if your project gets accepted into OWASP Labs
Please answer this question using up to 250 words, and no less than 200 words.
Additional Comments
Any additional comments or items you wish to bring to our attention.
Need assistance with this form?