[TASK] Improve severity mapping in `droopescan` parser

[utksh1]

Summary

droopescan parser results should map output severities more consistently into SecuScan finding severity levels.

Why this task exists

Plugin quality depends on metadata clarity, parser stability, and predictable capability declarations. This task should tighten one plugin or plugin family without changing unrelated plugin behavior.

Scope

• Suggested files or directories: plugins/droopescan/parser.py
• Out of scope: broad multi-plugin refactors unless directly required to complete the target plugin change

Starting points

Review adjacent plugin metadata and parser tests in plugins/ and testing/backend/ to mirror established patterns.

Acceptance criteria

• The target plugin metadata or parser contract is improved as described
• Tests or fixtures are added when parser behavior changes
• Documentation stays in sync with the plugin contract if operator behavior changes

Test plan

Run the plugin-specific pytest file if one exists, or add focused parser coverage under testing/backend/ for the changed behavior.

Notes for contributors

Keep fixture data minimal and representative. Avoid opportunistic edits to unrelated plugin directories.

[deepsikha-dash]

Hi @utksh1, I'd like to work on this issue under GSSoC'26.

Plan:

• Review the current severity mapping logic in plugins/droopescan/parser.py.
• Ensure Droopescan output severities are consistently translated to SecuScan severity levels.
• Add or update parser tests if behavior changes.
• Keep the changes scoped to the droopescan plugin only.

Please assign this issue to me. Thanks!

[madsysharma]

/assign
I would like to work on this as part of GSSoC 2026.