This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Template:ProjectAssessmentCriteria V2 Checklist

From OWASP
Revision as of 19:02, 22 June 2009 by Dinis.cruz (talk | contribs)

Jump to: navigation, search

This FORM is EDITED via a template

Alpha level

1. Is your tool licensed under an open source license?


{{{1. Is your tool licensed under an open source license?}}} {{{1.}}}

2. Is the source code and any documentation available in an online project repository? (e.g. Google Code or Sourceforge site)


{{{2. Is the source code and any documentation available in an online project repository?}}}

3. Is there working code?


Delete this text and place your answer here.

4. Is there a roadmap for this project release which will take it from Alpha to Stable release?


Delete this text and place your answer here.

Beta Level

5. Are the Alpha pre-assessment items complete?


Delete this text and place your answer here.

6. Is there an installer or stand-alone executable?


Delete this text and place your answer here.

7. Is there user documentation on the OWASP project wiki page?


Delete this text and place your answer here.

8. Is there an "About box" or similar help item which lists the following?

  • Project Name
  • Short Description
  • Project Release Lead and contact information (e.g. email address)
  • Project Release Contributors (if any)
  • Project Release License
  • Project Release Sponsors (if any)
  • Release status and date assessed as Month-Year (e.g. March 2009)
  • Link to OWASP Project Page

Delete this text and place your answer here.

9. Is there documentation on how to build the tool from source including obtaining the source from the code repository?


Delete this text and place your answer here.

10. Is the tool documentation stored in the same repository as the source code?


Delete this text and place your answer here.

Stable Level

11. Are the Alpha and Beta pre-assessment items complete?


Delete this text and place your answer here.

12. Does the tool include documentation built into the tool?


Delete this text and place your answer here.

13. Does the tool include build scripts to automate builds?


Delete this text and place your answer here.

14. Is there a publicly accessible bug tracking system?


Delete this text and place your answer here.

15. Have any existing limitations of the tool been documented?


Delete this text and place your answer here.