Is your feature request related to a problem? Please describe.
—

Describe the solution you'd like
When creating the detailed report, modify column "Impact of target OSS" to "Impacted OSS". Its content involves the component name and version.

Describe alternatives you've considered
—

Additional context
—

Epic Description

This feature will generate a summary report in HTML and XLSX format from a collection of OSS vulnerability results in XLSX format.

List of Tasks (Complete in order)

• #5
• #6
• #7
• #8
• #9
• #10
• #11
• #12

Is your feature request related to a problem? Please describe.
Some items are removed because the rule for removal only considers the vulnerability ID.

Describe the solution you'd like
Include to the condition for removing duplicates the columns e and f (component name and version) aside from the vulnerability ID.

Describe alternatives you've considered
—

Additional context
—

Task Title

Task: Add GitHub Templates

Task Description

This task will add templates for creating GitHub issues and pull requests.

Epic Description

This feature will generate a detailed report in HTML and XLSX format from a collection of OSS vulnerability results in XLSX format.

List of Tasks (Complete in order)

• #22
• #23
• #24
• #25
• #26

Task Description

This task will clean the code and add documentation.
Make sure to check if the output results are still functional and correct.

Task Description

This task will use pandas Themes to format/style the summary report.

Task Description

This task will use DataTables to format/style the summary report.

Task List

• #20
• #21

Task Description

This task will simplify the implementation of BDSA severity. Currently, the severity is calculated but it can actually be looked up on the excel file.

Task Title

Feature: Setup project on GitHub

Task Description

This task will setup the project on GitHub by initializing a git repository, uploading it to GitHub, and creating initial issues/milestones.

Task List

• #27
• #28

Epic Description

This Feature will automate the scraping of components' latest version.
Previously, the component-latest version mapping is inside the config file.
It must be separated to another file (preferably as an excel file).

Also, there must be testing made to check if latest version is different than the current version (note that its different and not higher because that's impossible with different versioning styles). For now, just take note about it because I don't know what to do with this.

List of Tasks (Complete in order)

1. Task: Migrate latest version mapping to excel

Is your feature request related to a problem? Please describe.
—

Describe the solution you'd like
Change the value of "Internet Exposure" column to maru/batsu when generating the report.

Describe alternatives you've considered
—

Additional context
—