Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork4.1k
Workaround for GitHub API to retrieve dependabot alerts per branch#13182
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Draft
mkurz wants to merge1 commit intoplayframework:mainChoose a base branch
base:main
Could not load branches
Branch not found:{{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline, and old review comments may become outdated.
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This file contains hidden or 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
This was referencedMar 10, 2025
e79fcfc to349079bCompareNews from GitHub:https://github.blog/changelog/2025-03-26-transitive-dependencies-are-now-available-for-maven/ Also, actually I have an idea for another workaround.... but not working on it now. |
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Labels
None yet
1 participant
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.
I think knowing which vulnerabilities we have/ship in our dependencies in our stable branches isvery important. But currently GitHub does not support non-default branches with their Dependabot alerts.
So, time to make the impossible possible ;)
ref,shaand the manifests'source_locationattributes in the JSON that will be submitted scalacenter/sbt-dependency-submission#249If you have a repo that hosts apackage ecosystem that is supported by GitHub's dependency graph api (like node or maven), GitHub (can) automatically scan a repos' manifest file(s) and create a dependency tree and dependabot alerts from that.
The current problem is, only the default branch of a repo is currently supported. There is no way to make GitHub scan a non-default branch (e.g. in our case that would be the stable 3.0.x and 2.9.x branch).
Further, GitHub does not support Scala (sbt) project's out of the box, so that's why sbt-dependency-submission exists.
We have workflows setup up with that action in the 2.9.x and 3.0.x branch. However, currently, they are useless. They do not submit anything to GitHub, GitHub just ignores the JSON it generates.
That means, the alerts we see athttps://github.com/playframework/playframework/security/dependabotonly cover the main branch.
However, how do we see if there is a vulnerability in a dependency in the 3.0.x branch? And how could we distinguish the branches in the "Dependabot alerts" page referenced above? After alot of research how the GitHub dependency submission API works I am pretty sure It's possible to make GitHub api do what we want. Please take a look atscalacenter/sbt-dependency-submission#249 where I also posted a screenshot.