Hey everyone, I'm facing a challenge with the npm registry. I found out that there's an organization with the exact same name as my company, which complicates things for us. We started releasing packages without namespacing them due to some urgency. I know there's a process to file a name dispute with npm, but it's been months since I submitted my ticket in May, and I haven't received any response at all. I've tried to follow up, but still nothing. So, I'm wondering if anyone has advice on how to resolve this issue or escalate it further if necessary?
3 Answers
I totally get where you’re coming from, but you can’t just assume you can take a name because you think the other person isn’t using it. There could be many reasons they haven’t published anything yet, like using it for private packages or future projects. Instead of trying to claim their namespace, maybe think about alternatives like adding a suffix to your company name, such as appleDev or appleTeam. Disputes should really only happen when there’s clear trademark evidence.
Honestly, I’m a paid user on GitHub, and I often find they ignore support tickets too, so it doesn’t surprise me they haven’t gotten back to you.
Having the same name as another entity doesn’t necessarily mean there’s a name dispute. If the other party has registered the name in bad faith, that might be different. If they’ve published packages that are already dependencies, it’s unlikely they’ll change it. You might just want to consider using a different name; it's not a huge deal, and people probably won't notice.
What if the org name actually infringes on a trademark? That’s a big deal and could force npm to change things, right?
But our company is not small – we’re a large enterprise with thousands of employees. Should we really just rebrand? It seems someone from my old team might have claimed the npm org and then left. No packages exist under that organization, so wouldn’t it be reasonable to get that access?