npm access public orange-orm

[lroal]

Select Topic Area

Bug

Body

I'm unable to publish updates to my own package orange-orm despite being the owner. I consistently get a 403 Forbidden error, but I CAN successfully publish scoped packages like @lroal/orange-orm-test.
Package details:

Package name: orange-orm
Current version on npm: 4.7.14
Attempting to publish: 4.7.15
Package owner verification: npm owner ls orange-orm returns lroal [email protected] (me)

What I've tried:

✅ Confirmed I'm logged in: npm whoami returns lroal
✅ Created new tokens (Neith Classic nor Granular Access Token worked, no IP restrictions)
✅ Token is properly set (shows as "protected" in config)
✅ Successfully published a test scoped package @lroal/test-package
✅ Verified package.json version (4.7.15) is not already published
✅ Package size is reasonable (837KB)
✅ Tried with and without OTP
❌ Cannot publish to orange-orm specifically

npm error code E403
npm error 403 403 Forbidden - PUT https://registry.npmjs.org/orange-orm
npm error 403 In most cases, you or one of your dependencies are requesting
npm error 403 a package version that is forbidden by your security policy, or
npm error 403 on a server you do not have access to.

This suggests there's something specifically blocking the orange-orm package that I cannot see or resolve on my end. The package has been published successfully for years until now.

Questions:

Is there a security flag or hold on the orange-orm package?
Are there any account or package-level restrictions I cannot see?
How can I resolve this to continue maintaining my package?

Thank you for any help!

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

[lroal]

Yes, I have tried all suggestions above and reported to npm support yesterday.
Haven't heard from them yet.

Btw: ls-packages was not recognized, had to use: npm access list packages
(It showed read-write for lroal)