[EdgeBit] Create an SBOM for Vulnerability Scanning #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![edgebitstaging[bot]](https://avatars.githubusercontent.com/u/110495705?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR enables vulnerability scanning by producing a Software Bill of Materials (SBOM) for this repository. The SBOM will be created by looking at the packages installed (eg. scanning files like
requirements.txtorpackage.lock) and matching them to vulnerabilities by uploading it to EdgeBit. If issues are found in dependency changes, a comment will be made with more info. Otherwise, the bot is silent — but you can view cumulative results at any time.EdgeBit is real-time SCA connected to your server fleet, so it understands which code is active or dormant in this app. Vulnerabilities in dormant code are deprioritized to save you time.
If this project builds a container with GitHub Actions, EdgeBit was not able to detect it.
Building an SBOM from the container is preferable since it creates a more complete vulnerability report. If this project builds a container, consider closing this PR and adding a workflow step to generate an SBOM. See https://edgebit.io/docs/0.x/install-build-actions/ for details.