Roadmap

After all, dradis is still a young project, there is lots of room for improvement. A small summary of what is in the pipeline for the next releases:

Game-chaging features:

• The Meta Server: a central repository of projects to which dradis teams can upload their results once they have completed an engagement. Useful to hold a database of old projects to quickly run a re-test or answer a question from a client about a six month old project.
• Provide a Virtual Machine with the Meta Server and a Vulnerability Database already configured.
• Custom field definition. The ability to choose the different fields your notes would consis of. Instead of the current Text/Author/Category fields you could your own (Probability, CVSS num., etc.) [v3.0]
• Finish up the Multiverse.

Incremental improvements:

• Adding some sort of formatting to the notes.
• RSS feed of changes. Provide a team lead view that shows latest changes.
• Upgrade to the latest Rails and ExtJS
• Ensure we support Ruby 1.9
• Provide a configuration interface for server plugins
• Improve feedback for upload plugins: upload progress, errors, etc.
• Create a upload plugin for Burp Scanner output files.
• Improve the Windows installer:
  • Present a nice splash screen
  • Use our logo for the icons in the shortcuts.
  • Add a shortcut to the web interface.
  • Provide a way to launch the server and a browser to the web interface.

Things that once were in the Roadmap and were implemented in previous releases:

• Import from file. A framework to support importing content from files (for example, nmap or nessus output files) into the repository from the web interface. [done]
• Import/export projects (think backup). [done]
• Add a flexible reporting module to export to WordXML or pdf. [done]
• Add the ability to import notes from external sources (i.e. vulnerability database). [done]
• It should be possible to add attachments (screenshots, tool output files, etc.) to the nodes. [done]

If you want to know more about any of this modules or cannot wait to start contributing with some awesome code, join the mailing lists now!

There is also a TODO file in the subversion repository of the project. This file is used by the development team to keep track of what needs to be done an when.