You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dependabot convinces contributors that CVE reports are private when in fact they are quite public.
Specifically, Dependabot hides reports to non project owners. But anyone can already fork (either with ordinary GitHub controls, or manually), and then see the exact same CVE information at the fork. So it only hurts contributors of the main fork to hide actionable CVE reports.
If GitHub is too lazy to implement RBAC for Dependabot Web UI widgets, that's one thing. But logically, there is no good reason to hide the security tab from anyone with read privileges on the repository, nevermind their status as owner or not.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Dependabot convinces contributors that CVE reports are private when in fact they are quite public.
Specifically, Dependabot hides reports to non project owners. But anyone can already fork (either with ordinary GitHub controls, or manually), and then see the exact same CVE information at the fork. So it only hurts contributors of the main fork to hide actionable CVE reports.
If GitHub is too lazy to implement RBAC for Dependabot Web UI widgets, that's one thing. But logically, there is no good reason to hide the security tab from anyone with read privileges on the repository, nevermind their status as owner or not.
Beta Was this translation helpful? Give feedback.
All reactions