Generate Extensive Reports for cve-bin-tool | Stage 1 ( add as an output type )

[SinghHrmn]

About

We will first add the HTML report as an output type. After we are able to generate HTML reports we will look forward to generating the HTML reports by comparing it with other files.

Stage1

Start with a template for Extensive Report. It will have the following checkpoints.

• Creating Template
• Refactor Template to smaller Sub Parts
• Generate template from actual data

ScreenShots for templates

CVE Binary tool Main Dashboard.

List of Products with Known CVEs

As the template is ready I will move towards refactoring the files to smaller subfiles.
We want to divide the code into smaller sections because we will need to swap some components on the basis of what scans we are doing. Possibly when we are comparing changes.

[SinghHrmn]

Work in Progress

Currently, a html_reports directory with templates has been created and is linked to the architecture of the OutputEngine.py a dummy data is included inside OutputEngine and that refers to the structure of data needed to generate the report. So if the dummy data is replaced with scanned data the Report Generation process will start working.

The template is responsive and the design changes on small and extra small screen sizes.

I'm also working on the feature to filter the data based on product names with a specific version. The feature is WIP. So now the major work left is to to get the data from the tool.

I'll start looking to find out how cve.db is working and how to generate the data I needed.

My priority is to first at least generate data from the tool. After that, I'll start enhancing HTML by adding accessibility such as screen reader support.

[SinghHrmn]

Now the Report can be generated from the scan_data. But currently the tests are failing due to updation of formatted_output function.