Feedback for the “Private Vulnerability Reporting” tab #213485
Unanswered
gpotter2
asked this question in
Code Security
Replies: 1 comment
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Product Feedback
💬 Feature/Topic Area
Code quality
Discussion Details
Hi!
I've been using the "Private Vulnerability Reporting" feature quite a lot recently, since it has become one of the main ways people report security issues to us. I read Maintainers don’t need more AI bug reports. They need fixes. earlier today, and while I agree with a lot of it (and think it's a cool initiative), it made me think about my experience receiving bug reports on GitHub. The "Private Vulnerability Reporting" experience is honestly pretty terrible right now, and I think the maintainer side needs some love. To try to be constructive, I've put together some feedback on the things I think need the most improvement:
is:securityfilter?).It's not clear what happens if I click the "Request CVE" button. Given the number of AI reports, I also wonder if GitHub is still assigning CVE numbers (we haven't received any for recent reports, unlike a few years ago). If this has been abandoned (which would be fair TBH), maybe remove that button? Or at least give us a bit more context about what's happening.
When merging the patch from a report, it has a hardcoded "Merge commit from fork" message, which you cannot change. You can only select "Merge" (not rebase / squash) which means you also necessarily end up with an unreadable blob of a commit (like secdev/scapy@8db9853) :(
I might have more ideas later, but that sounds like a good start 😄 Have a good week !
All reactions