OWASP wpBullet

Instructions are in RED text and should be removed from your document by deleting the text with the span tags. This document is intended to serve as an example of what is required of an OWASP project wiki page. The text in red serves as instructions, while the text in black serves as an example. Text in black is expected to be replaced entirely with information specific to your OWASP project. Project About PROJECT INFO What does this OWASP project offer you? RELEASE(S) INFO What releases are available for this project? what is this project? Name: WpBullet Purpose: wpBullet is a source code analysis framework capable of identifying security flaws in WordPress extensions (themes & plugins) or any other codebase which uses WordPress API functions. License: GNU General Public License v2.0 who is working on this project? Project Leader(s): Luka Sikic Project Contributor(s): Nikola Gigic how can you learn more? Project Pamphlet: Not Yet Created Project Presentation: Mailing list: [global-projects-committee Mailing List Archives] Project Roadmap: [Global_Projects_Committee View] Main links: OWASP wpBullet on Github Key Contacts Contact Luka Sikic to contribute to this project Contact Luka Sikic to review or sponsor this project current release The current release can be found at GitHub repository last reviewed release The last reviewed release can be found at GitHub repository other releases Description This is where you need to add your more robust project description. A project description should outline the purpose of the project, how it is used, and the value it provides to application security. Ideally, project descriptions should be written in such a way that there is no question what value the project provides to the software security community. This section will be seen and used in various places within the Projects Portal. Poorly written project descriptions therefore detract from a project’s visibility, so project leaders should ensure that the description is meaningful. The Tool Project Template is simply a sample project that was developed for instructional purposes that can be used to create default project pages for a Tool project. After copying this template to your new project, all you have to do is follow the instructions in red, replace the sample text with text suited for your project, and then delete the sections in red. Doing so should make it clearer to both consumers of this project, as well as OWASP reviewers who are trying to determine if the project can be promoted to the next category. The information requested is also intended to help Project Leaders think about the roadmap and feature priorities, and give guidance to the reviews as a result of that effort. Creating a new set of project pages from scratch can be a challenging task. By providing a sample layout, with instructional text and examples, the OWASP Tool Project Template makes it easier for Project Leaders to create effective security projects and hence helps promote security. Contextual custom dictionary builder with character substitution and word variations for pen-testers Licensing A project must be licensed under a community friendly or open source license.  For more information on OWASP recommended licenses, please see OWASP Licenses. While OWASP does not promote any particular license over another, the vast majority of projects have chosen a Creative Commons license variant for documentation projects, or a GNU General Public License variant for tools and code projects. This example assumes that you want to use the AGPL 3.0 license. This program is free software: you can redistribute it and/or modify it under the terms of the link GNU Affero General Public License 3.0 as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. OWASP XXX and any contributions are Copyright © by {the Project Leader(s) or OWASP} {Year(s)}. Roadmap As of November, 2013, the highest priorities for the next 6 months are: Complete the first draft of the Tool Project Template Get other people to review the Tool Project Template and provide feedback Incorporate feedback into changes in the Tool Project Template Finalize the Tool Project template and have it reviewed to be promoted from an Incubator Project to a Lab Project Subsequent Releases will add Internationalization Support Additional Unit Tests Automated Regression tests Getting Involved You can contribute to the project on GitHub repository. If you have any questions feel free to reach out at luka [ at ] sikic.eu Project Leader Luka Sikic Classifications