Debendabot security alerts support for vcpkg

[nyoma-diamond]

Select Topic Area

Product Feedback

Body

I had originally posted this as an issue on the dependabot repo (dependabot/dependabot-core#13325), but was suggested to also place it here.

This is likely already in consideration for Dependabot given vcpkg support is new as of August, given that it's not currently on the public roadmap and there haven't been any issues on the original repo (other than my own) nor discussions about it here, I thought I'd specifically request security alerts be implemented for vcpkg.

Currently, projects moving from other ecosystems (e.g., NuGet) to vcpkg end up losing security alerts. However, switching to vcpkg is particularly valuable as (A) some extremely useful libraries are available via vcpkg but not NuGet, and (B) the ability to build dependencies on an ad-hoc basis enables much better cross-platform support for projects. However, particularly for the latter of these, this also introduces some new potential vectors for security vulnerabilities to appear. This being the case, I think it is very prudent that security alerts be implemented for vcpkg.

Additionally, are there specific potential complications regarding security alerts for vcpkg projects that may want to be considered? Given vcpkg dependencies being built on an ad-hoc basis, I could potentially see circumstances where vulnerabilities appear at build-time that may not be possible to implement or track in Dependabot that probably ought to be documented.

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐