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.
🏷️ Discussion Type
Bug
Body
Summary
My GitHub profile continues to display an orphaned GHCR package named
av-sort, despite the package no longer being accessible or manageable through the GitHub UI or REST API.This issue has persisted for more than five months.
Environment
Yaoser-xYQuarkghcr.io/yaoser-x/av-sortReproduction and verification
av-sortentry is still visible.GET /user/packages/container/av-sortusing an authenticated GitHub CLI session withread:packages. The API returns404 Package not found./user/packages?package_type=container. The current package list contains onlyfolder-integrity, notav-sort.There were historical username changes and repository/organization transfers involving this package name.
Expected behavior
The orphaned
av-sortentry should be removed from my public Packages tab and related search indexes.I am not requesting package restoration. I only want the stale public entry removed.
Previous support requests
Both tickets remain Open without a human response as of October 31, 2026.
Related issue
https://github.com/orgs/community/discussions/188590
A similar stale package metadata problem was reportedly resolved by a server-side data refresh in March 2026.
Could the GitHub Packages team investigate whether a similar metadata or cache refresh could resolve this orphaned entry?
Thank you.


All reactions