Replies: 9 comments 4 replies
-
I have the same issue with GHSA-mc52-jpm2-cqh6, but I didn't create the advisory, but was instead credited for finding and reporting it. However, just like OP, there isn't a badge on my profile either. |
Beta Was this translation helpful? Give feedback.
-
+1 Having the same issue with GHSA-wxrm-jhpf-vp6v |
Beta Was this translation helpful? Give feedback.
-
I have the same issue with my vulnerability reports (GHSA-5prv-r7jg-vrf7, GHSA-xmw2-875x-rq88, GHSA-jhrq-qvrm-qr36, GHSA-qqrm-9grj-6v32, GHSA-2vxv-pv3m-3wvj and GHSA-f7g9-xhcq-5ww6). So far, the common factor among advisories displayed on profile pages AFAICT is that they are labeled as But that is weird given that the documentation of the badges doesn't mention anything about GitHub-reviewed advisories. If that were really the requirement for being displayed in the profile page, I think the documentation should be updated to mention that requirement at least. |
Beta Was this translation helpful? Give feedback.
-
Same issue here with my report GHSA-cj3c-5xpm-cx94 - And it was assigned a CVE so it was reviewed by github, right? |
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Still not fixed for me |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
Finally, the issue got resolved for me. So for anyone having the same issue: Contacting GitHub Support does the trick ^^ |
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
Hello!
According to the docs here, if a submitted security advisory is accepted, you'll get a Security advisory credit badge on your profile. In the past, I have submitted and been credited for GHSA-f8m6-h2c7-8h9x. If I hover over my name in the credits section of that advisory, it says: "1 security advisory credit".
However, despite having this advisory credit, the credit is not displayed on my profile. I do know that it is possible for users to get this info in their Highlights section with just one credit, as I have seen it on other profiles, e.g. https://github.com/robmcl4.
So, my first question is, how can I display my security advisory credit on my profile?
Additionally, I have a second question. In the past, other advisories have been made and published by other CVE Numbering Authorities (CNA), like GHSA-2ww3-fxvq-293j. This vulnerability was resolved by me, but I am not credited in the advisory. Is there something I can do about that?
Thanks all.
Beta Was this translation helpful? Give feedback.
All reactions