feat: Vulnerability Scanning

[jay-dee7]

Motivation & Context:

reason/motivation behind the PR, context of what problem it solves
This PR solves the issue #issue

Description:

describe the change briefly

Types of Changes:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

PR Checklist:

• My code follows the code style of this project
• My change requires a change to the documentation
• I have updated the documentation accordingly
• I've read the CONTRIBUTION guide
• I have signed-off my commits with git commit -s

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
Once a secret has been leaked into a git repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}