Submit sbt dependencies to GitHub for vulnerability monitoring #32
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
![gu-dependency-graph-integrator[bot]](https://avatars.githubusercontent.com/u/164318?s=60&v=4){kind=small}
gu-dependency-graph-integrator
bot
requested a review
from a team
as a code owner
Following the PR checklist, I’m removing the test branch trigger as it’s no longer needed.
Now that we’re sending the dependencies to github, we no longer need to send them to snyk.
emdash-ie
approved these changes
Jan 6, 2025
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.
What does this change?
This PR sends your sbt dependencies to GitHub for vulnerability monitoring via Dependabot. The submitted dependencies will appear in the Dependency Graph on merge to main (it might take a few minutes to update).
What do I need to do?
sbt-dependency-graph-a2e99e68b739b516was created. Sense check the output of the step "Log snapshot for user validation", and make sure that your dependencies look okay.sbt-dependency-graph-a2e99e68b739b516from the filesbt-dependency-graph.yaml(aka delete line 6), approve this PR, and merge.Why?
If a repository is in production, we need to track its third party dependencies for vulnerabilities. Historically, we have done this using Snyk, but we are now moving to GitHub’s native Dependabot. Scala is not a language that Dependabot supports out of the box, this workflow is required to make it happen. As a result, we have raised this PR on your behalf to add it to the Dependency Graph.
How has it been verified?
We have tested this workflow, and the process of raising a PR on DevX repos, and have verified that it works. However, we have included some instructions above to help you verify that it works for you. Please do not hesitate to contact DevX Security if you have any questions or concerns.
Further information for sbt
See the sbt workflow documentation for further information and configuration options.