Replies: 2 comments
|
You can check npm’s official package name dispute policy and support page for guidance. I’d recommend waiting for npm Support’s response and explicitly asking whether they can forward a voluntary transfer request to the owner’s registered email without disclosing their private contact details. Good luck with Nitro! |
|
Hi Marc, You've already taken the right steps by contacting the package owner and npm Support. I’d recommend continuing through npm’s official support channel and asking whether they can forward a voluntary transfer request to the current maintainer without disclosing their private contact information. You can also check npm’s official package name dispute and ownership policies to understand what options are available. Since inactivity alone may not justify transferring a package, it’s best to frame this as a request to contact the owner rather than a request to claim the name. If the maintainer cannot be reached, npm Support is the appropriate place to ask what alternatives, if any, are available. Keep your existing correspondence and the public evidence of your attempts to contact the owner. Hope you can get in touch with them and find a solution! Official resource: https://www.npmjs.com/support |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
Body
Hi npm team,
I'm Marc, the creator of Nitro, an actively maintained project for building native modules for React Native. It's published as
react-native-nitro-modulesand had about 8.5 million npm downloads between September 13 and October 12.I'd love to use the shorter
nitro-modulesname and ask its owner whether they'd be willing to transfer it. The package metadata listsnitro_as its sole maintainer and May 14, 2018 as its last publication date. The public email isinfo@nitroh.io, but that domain no longer resolves. I couldn't find another public email in their npm packages or Git history.I opened an issue asking the owner today, October 15, and have also submitted a request through npm Support.
I understand that inactivity alone isn't grounds for reassigning a package. Can npm forward a voluntary-transfer inquiry to an owner's registered contact address, if a working one is available? Has anyone used a supported process for this when the public email no longer works?
Thanks!
Marc
All reactions