uv.lock root package name triggers false-positive Dependabot alerts

[dikesh]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Dependabot

Discussion Details

Bug Description

Dependabot / Dependency Graph incorrectly assigns vulnerability alerts to a repository when its root package name declared in uv.lock matches a public PyPI package name, even when zero vulnerable dependencies are installed.

Reproduction Repository

https://github.com/dikesh/dependabot-bug-test

Steps to Reproduce

1. Create or fork a Python project using uv.lock (or fork the reproduction repo above).
2. Set the root package name = "<public-package-name>" (e.g., meta-ads-mcp) inside uv.lock.
3. Do not declare or install any vulnerable dependencies.
4. Enable Dependabot Alerts on the repository.

Observed Behavior

Dependabot treats the root package declaration in uv.lock as an unversioned vulnerable dependency. As a result, it triggers false-positive alerts matching public PyPI advisories (such as https://github.com/pipeboard-co/meta-ads-mcp/security).

Expected Behavior

Dependency Graph should recognize the root [[package]] entry in uv.lock as the local project itself and verify version resolution before triggering security alerts.

Workaround

Changing the local project/package name in uv.lock clears the false-positive alerts immediately.

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