OWASP Project Assessment Criteria
General criteria for assessing Tools, Code or Document OWASP projects
Sign in to Google to save your progress. Learn more
Name of the project *
write name of the project to be assesed
Project Leader(s) *
Please specify if more than one
Reviewer's name *
First and Lastname
Reviewer email (in case other than the one you are submitting with)
Relationship to the project
Project URL
Date of assesment *
MM
/
DD
/
YYYY
Assessment completion time
Time that took you to fill in the form in minutes
1.1-Does the wiki template have the minimum standard wiki content (project overview, description, etc. like the appropriate sample project template), and is it updated with releases? *
Required
1.2 Does the project have an active project leader? (Maintains project site with news and release announcements, continually enhancing the project, promoting the project to the security *
Required
1.3-Is the project maintained with the current operating systems and technology? *
Required
1.4-Does the project demonstrate progress to the community and verify that development is on track with a roadmap? *
Required
2.1-Does the project have a good track record of resolving issues and answering questions from project consumers? *
Required
2.2-Does the project address a security concern?  (Leader should state in their overview or summary what security concern they are addressing) *
Required
3.1-Does the project use an appropriate Community Friendly License? *
Required
3.2-Are project deliverables, information, and releases readily available and accessible to the public?  (Note: this can be a link to the repository, or a link to an external web site) *
Required
3.3-Do the Project Leaders follow operate ethically?  (For example, see the Project Leader Handbook Code of Ethics section 8.3, cited below or available online at https://www.owasp.org/images/6/6a/OWASP_Projects_Handbook_2013.pdf) *
Required
3.4-Doe the project leaders and contributors treat everyone with dignity and respect?  (Note: Input from the community may be required or use input from the community) *
Required
3.5-Is the project vendor neutral? *
Required
3.6-Does the project provide an innovative approach to address a security concern within the industry? *
Required
4.1-Does the project have a release? *
Required
4.2-Is the project release categorized as beta or stable? *
Required
Submit
Clear form
Never submit passwords through Google Forms.
This form was created inside of OWASP Foundation.

Does this form look suspicious? Report

Google Forms