npm never responds to my question regarding org name squatting

[hgl]

Select Topic Area

Question

Body

I tried both the npm support form and sending to support email support@npmjs.com. I waited for each for more than a week and then tried the next method.

Got no response so far.

The npmjs name policy page says

Organization names are considered squatted if there are no packages published within a reasonable time.

We would like to claim an org name that appears to be unused, with no published packages.

Could any staff member help us? Thanks.

[mecodeatlas]

Hi there, @hgl! 👋

Thanks for reaching out.

npm organization name disputes are handled according to the official dispute policy. At this time, org names can only be reviewed if there is a valid trademark associated with the name.

If you hold a registered trademark for the name, you may submit a trademark request through GitHub Support’s trademark request form.

If there isn’t a registered trademark involved, unfortunately there isn’t a process available to claim an unused organization name.

Let us know if you have any other questions.

[lukebarton]

If there isn’t a registered trademark involved, unfortunately there isn’t a process available to claim an unused organization name.

This is disappointing. I am in exactly this spot. Someone squatting on a perfectly good organisation name, and it would cost me £170 to apply for a trademark just to get you to act on it.

[ppoulard]

@mecodeatlas
Hello, what about package squatting ?
I would like to publish under a name that is obviously in violation with npm policy : https://docs.npmjs.com/policies/disputes

"Package names are considered squatted if the package has no genuine function."

The actual package was published 9 years ago, has 0 dependencies and dependants, contains a README file with 3 lines, a default package.json, and an empty file src/index.ts