geodot - similar to - reodkt?

[ArgusPano]

🏷️ Discussion Type

Bug

Body

Hello.

Is this a mistake in your similar-name detector?

geodot is not at all similar to reodkt.

Log:

npm notice Publishing to https://registry.npmjs.org/ with tag latest and public access
npm notice publish Signed provenance statement with source and build information from GitHub Actions
npm notice publish Provenance statement published to transparency log: https://search.sigstore.dev/?logIndex=1853424815
npm error code E403
npm error 403 403 Forbidden - PUT https://registry.npmjs.org/geodot - Package name too similar to existing package reodkt; try renaming your package to '@arguspano/geodot' and publishing with 'npm publish --access=public' instead
npm error 403 In most cases, you or one of your dependencies are requesting a package version that is forbidden by your security policy, or on a server you do not have access to.

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

[Amorfati123]

This does look like a false positive to me. geodot and reodkt are the same length, but they do not seem visually or phonetically close enough to be an obvious typosquatting risk.

The scoped-package suggestion makes sense as a workaround, but it does not really answer whether the similarity detector is being too aggressive here.

It might help npm/GitHub staff if you include whether reodkt is active/popular and whether you tried publishing as @arguspano/geodot. If scoped publishing works but unscoped does not, that would make the issue clearer.

[maheerCodes]

hey @ArgusPano 👋.
yeah this looks like a false positive ,,,geodot and reodkt dont share any obvious visual or phonetic similarity.the detector seems to be matching on characterr composition or length rather than actual visual resemblance.

npms typosquatting detector uses an algorithm that checks things like :

• same character set(both use g,e,o,d,t and r,e,o,d,k,t ,,,they share e,o,d,t).
• same length( both 6 characters) .
• similar letter frequency patterns,

so technically the algorithm is working as designed,,,,,but the design itself is too aggressive here. geodot and reodkt wouldnt confuse any real user.
for now the quickest fix is the scoped package route ,,,publish as @arguspano/geodot ,this bypasses the unscoped name conflict entirely and is actuallly the better long-term approach anyway for namespace clarity.
if you want the unscoped name specifically ,you can open a support ticket at github.com/contact or reach out to npm support directly ,,, if reodkt is inactive /unpopular they can sometimes manually approve an exception. checking if reodkt has any downloads on npmjs.com /package/reodkt would help your case,,,,,,