Configure WhiteSource Bolt for GitHub

[mend-bolt-for-github]

Welcome to WhiteSource Bolt for GitHub! This is an onboarding PR to help you understand and configure settings before WhiteSource starts scanning your repository for security vulnerabilities.

🚦 WhiteSource Bolt for GitHub will start scanning your repository only once you merge this Pull Request. To disable WhiteSource Bolt for GitHub, simply close this Pull Request.

---

What to Expect

This PR contains a '.whitesource' configuration file which can be customized to your needs. If no changes were applied to this file, WhiteSource Bolt for GitHub will use the default configuration.

Before merging this PR, Make sure the Issues tab is enabled. Once you merge this PR, WhiteSource Bolt for GitHub will scan your repository and create a GitHub Issue for every vulnerability detected in your repository.

If you do not want a GitHub Issue to be created for each detected vulnerability, you can edit the '.whitesource' file and set the 'minSeverityLevel' parameter to 'NONE'.

---

❓ Got questions? Check out WhiteSource Bolt for GitHub docs.
If you need any further assistance then you can also request help here.

[ChariPramod]

Hi Team,

I've reviewed the initial onboarding pull request from WhiteSource Bolt for GitHub and everything looks set to move forward. This PR includes the .whitesource configuration file which is currently set with the default settings. This integration will enable us to scan our repository for security vulnerabilities, which is crucial for maintaining our codebase's security integrity.

Key Points:
Activation: WhiteSource Bolt will start scanning our repository for vulnerabilities as soon as we merge this PR.
Issue Reporting : By default, WhiteSource Bolt will create GitHub Issues for every vulnerability detected. If we prefer to manage notifications differently, we can adjust the minSeverityLevel in the configuration file.
No Conflicts : There are no merge conflicts with the base branch, indicating a smooth integration process.

Please review this PR at your earliest convenience. If everything is in order, I recommend merging it to activate our repository scanning. This step is vital for enhancing our security measures and staying proactive about vulnerability management.

Thank you for your attention to this matter!

Best regards,
Pramod