Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure Mend Bolt for GitHub #375

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mend-bolt-for-github[bot]
Copy link

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

🚦 Mend Bolt for GitHub will start scanning your repository only once you merge this Pull Request. To disable Mend 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, Mend Bolt for GitHub will use the default configuration.

Before merging this PR, Make sure the Issues tab is enabled. Once you merge this PR, Mend 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 Mend Bolt for GitHub docs.
If you need any further assistance then you can also request help here.

@MaisiKoleni
Copy link
Collaborator

MaisiKoleni commented Aug 17, 2024

Is there a reason for this, meaning any action from our side? Otherwise I would categorize this as spam / cold calling and close the PR. @krusche @MarkusPaulsen

@b-fein
Copy link
Contributor

b-fein commented Aug 17, 2024

/cc @FelixTJDietrich since it seems to be used in ls1intum/Hephaestus#51

@FelixTJDietrich
Copy link

It was activated on org level by @krusche, I just merged it in Hephaestus and it created some security issues. I thought we are supposed to merge it 🤔

@krusche
Copy link
Member

krusche commented Aug 18, 2024

yes, we want to try it out and see if it helps identify additional security vulnerabilities in dependencies. @MaisiKoleni you can ignore it ;-) we will take care

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants