OWASP Joomla Vulnerability Scanner Project - Assessment Frame - First Review - Self Evaluation - A

From OWASP
Jump to: navigation, search

Click here to return to the previous page.

OWASP JOOMLA VULNERABILITY SCANNER PROJECT's SELF-EVALUATION
PART I
Project Deliveries & Objectives

OWASP Joomla Vulnerability Scanner Project's Deliveries & Objectives

QUESTIONS ANSWERS

1. At what extent have the project deliveries & objectives been accomplished? Having in consideration the assumed ones (see here), please exemplify writing down those of them that haven't been realised.

MISSION ACCOMPLISHED

2. At what extent have the project deliveries & objectives been accomplished? Having in consideration the assumed ones (see here), please quantify in terms of percentage.

MISSION ACCOMPLISHED

3. What kind of help is required either from the Reviewers or from the OWASP Community?

Review, Evaluation, Suggestion for Improvements
PART II
Assessment Criteria

OWASP Project Assessment Criteria

QUESTIONS ANSWERS

1. Having into consideration the OWASP Project Assessment Methodology (see here), which criteria, if any, haven’t been fulfilled in terms of Alpha Quality status?

Alpha Quality requires:
  • Agree to OWASP's open source license - yes
  • Main page must be on the OWASP website yes
  • Have code documented in Google Code or Sourceforge yes
  • Mailing List created yes
  • Solves a core application security need yes (Reason:Address Joomla! CMS vulnerabilities)

2. Having into consideration the OWASP Project Assessment Methodology (see here), which criteria, if any, haven’t been fulfilled in terms of Beta Quality status?

Beta Quality requires:
  • Have an easy installer yes (Just extract and run)
  • Include user documentation on OWASP Wiki Pages yes
  • Include documentation on how to build it from code N/A
  • Documentation stored with code N/A

3. Having into consideration the OWASP Project Assessment Methodology (see here), which criteria, if any, haven’t been fulfilled in terms of Release Quality status?

Release Quality requires:
  • Reasonably easy to use yes
  • Include online documentation to built into the tool N/A
  • Include scripts that facilitate building from source N/A
  • Publicly accessible bug tracking system yes
  • Run through Fortify and/or Coverity's source code review N/A

4. What kind of help is required either from the Reviewers or from the OWASP Community?

Any bug/feedback/suggestion for improvement.