Threat Dragon is a community project, and we are always delighted to welcome new contributors!
There are various ways to help out with Threat Dragon project. The roadmap for version 2.0 sets out what is needed to get to the new version of Threat Dragon, and we are looking for help and contributions.
When contributing:
- see if there is already an issue for wehat you want to do
- follow our Code of Conduct
- there are some notes for developers that are being added to as we go along
If you have a question or problem relating to using Threat Dragon then the first thing to do is to check the Frequently Asked Questions tab on the OWASP project page. Threat Dragon documentation is available online.
If this does not help then one of the leaders / collaborators should be able to help.
If you have found a bug then raise an issue on Threat Dragon.
It is worth checking to see if its already been reported, and including as much information as you can to help us diagnose your problem.
If you think you have found a vulnerability in Threat Dragon then please report it to our leaders / collaborators.
We are always very grateful to researchers who report vulnerabilities responsibly and will be very happy to give any credit for the valuable assistance they provide.
If you have a suggestion for new functionality then you can raise this request as an issue on Threat Dragon.
Worth checking to see if its already been reported, and include as much information as you can so that we can fully understand your requirements.
There is always lots of coding to be done! Threat Dragon welcomes contributions and issues: