I'm in the midst of database and route changes right now so I don't want to start immediately. Once the app is in a stable place, I want to prioritize the introduction of unit tests. I need to do the following:

• Identify a unit test library that I want to use
• Write a test that checks to see if the app returns a 200 for requests to /
• Report my findings here
• Create a new issue with a goal to increase code coverage if needed

The templates should include forms to create a new company at /company/create and a domain at /domains/create.

I should provide some sort of an abuse flag in my scanner's user agent string. It should include some contact information or a link to this repository so anyone concerned about my scans can contact me and ask me to stop.

Make some effort to prevent XSS or related issues stemming from content injection.

Once I review the licensing, I will formulate a plan for how I want to utilize the tools in my application. Ideally, I can fork both and include them as packages or submodules here (they should allow this). This would allow me to make changes to both and build a tighter integration with my app.

Report my findings here and create a new issue to track future work.

Begin working on the infrastructure to host this application once the basic functionality is in place. I will be ready to work on this bug when the following work is complete:

• Companies can be added and a listing can be retrieved
• Domains can be added under companies and a listing can be retrieved
• A specific domain can be clicked on to return an empty overview page (page content will be populated with plugin output later)
• The website should be locked behind some simple authentication until authorization and access control work is completed
• Celery tasks should function (domain enumeration triggered via /scan endpoint) and update database with scan results

With that functionality complete, I can evaluate the AWS infrastructure in this bug. This bug will be complete when I have a pipeline in place with automated testing, linting and deployment.

This is partially completed work. Make sure that the header and footer is consistently used and remove unnecessary code from the remaining templates.