Organization level security policy #184651
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. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Product Feedback
Body
Repositories can have a "Security Policy" (available at
https://github.com/<owner>/<project>/security/policy) which is nice. However, sometimes a security issue does not really reside in just one project, or a security researched found a vulnerability and only know the organization it is related to (but it's not clear which project specifically is affected). In these cases, and possibly more, it would be very useful to have "Security Policy" at the organization level (following existing conventions, possibly available athttps://github.com/orgs/<org>/security/policy).Beta Was this translation helpful? Give feedback.
All reactions