# Problems with npm publish, why is my node spam?

**URL:** https://discourse.nodered.org/t/problems-with-npm-publish-why-is-my-node-spam/40229
**Category:** Developing Nodes
**Created:** [2 February 2021 11:22 UTC](https://discourse.nodered.org/t/problems-with-npm-publish-why-is-my-node-spam/40229 "2021-02-02T11:22:27Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![iiot2k](https://avatars.discourse-cdn.com/v4/letter/i/8baadc/32.png) [@iiot2k](https://discourse.nodered.org/u/iiot2k)
#### Post date: [2 February 2021 11:22 UTC](https://discourse.nodered.org/t/problems-with-npm-publish-why-is-my-node-spam/40229/1 "2021-02-02T11:22:27Z")

</div>

Hi,  
I write lot of nodes for Node-Red .  
Since 2 days I want put this nodes to npm with **npm publish**.  
Every time I become following error:

403 Forbidden - PUT [https://registry.npmjs.org/node-red-contrib-xxxx](https://registry.npmjs.org/node-red-contrib-xxxx) - Package name triggered spam detection; if you believe this is in error, please contact support at [https://npmjs.com/support](https://npmjs.com/support)  
npm ERR! 403 In most cases, you or one of your dependencies are requesting  
npm ERR! 403 a package version that is forbidden by your security policy.

I contact npm, but no answer.

How can I solve this ?  
Is there an alternative to npm for Node-Red ?

Thanks for your help

---

<div class="post-metadata">

### Author: ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)
#### Post date: [2 February 2021 11:55 UTC](https://discourse.nodered.org/t/problems-with-npm-publish-why-is-my-node-spam/40229/2 "2021-02-02T11:55:37Z")

</div>

> [@iiot2k](#):
>
> 403 Forbidden

Hi @iiot2k,  
could it be that you are working an another computer? Then you might need to do login to npm once (see [here](https://stackoverflow.com/a/63613635))...

---

<div class="post-metadata">

### Author: ![iiot2k](https://avatars.discourse-cdn.com/v4/letter/i/8baadc/32.png) [@iiot2k](https://discourse.nodered.org/u/iiot2k)
#### Post date: [2 February 2021 12:22 UTC](https://discourse.nodered.org/t/problems-with-npm-publish-why-is-my-node-spam/40229/3 "2021-02-02T12:22:31Z")

</div>

Thank you for answer.  
No, I have only one computer.  
Yes I do login with **npm login** and than **npm publish**.  
npm make my 😡

---

<div class="post-metadata">

### Author: ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [2 February 2021 12:23 UTC](https://discourse.nodered.org/t/problems-with-npm-publish-why-is-my-node-spam/40229/4 "2021-02-02T12:23:06Z")

</div>

> [@iiot2k](#):
>
> Package name triggered spam detection

[node.js - npm publish failed with Package name triggered spam detection - Stack Overflow](https://stackoverflow.com/questions/48668389/npm-publish-failed-with-package-name-triggered-spam-detection)

---

<div class="post-metadata">

### Author: ![iiot2k](https://avatars.discourse-cdn.com/v4/letter/i/8baadc/32.png) [@iiot2k](https://discourse.nodered.org/u/iiot2k)
#### Post date: [2 February 2021 14:53 UTC](https://discourse.nodered.org/t/problems-with-npm-publish-why-is-my-node-spam/40229/5 "2021-02-02T14:53:10Z")

</div>

Hi,  
The name in _package.json_ was: **node-red-contrib-redplc-rpi-pcf8575**  
npm reports it as spam.  
I change the name to **node-red-contrib-redplc-pcf8575-rpi**  
Same npm reports it as spam.  
I change the name to **node-red-contrib-pcfxxxx-redplc**  
Publish successfully.  
npm don't like numbers in packet name and recognizes as spam.  
Stupid npm 😡 the name of chip is pcf8575, which name should I use ?

---

<div class="post-metadata">

### Author: ![iiot2k](https://avatars.discourse-cdn.com/v4/letter/i/8baadc/32.png) [@iiot2k](https://discourse.nodered.org/u/iiot2k)
#### Post date: [2 February 2021 15:49 UTC](https://discourse.nodered.org/t/problems-with-npm-publish-why-is-my-node-spam/40229/6 "2021-02-02T15:49:39Z")

</div>

npm publish works now.

This is the answer of npm:

Hello,

Thanks for reaching out.

We've initiated some blocks related to package names. Our hope is this will help with both security and spam concerns we're facing.

As support, we're able to move beyond the block. I've published `node-red-contrib-redplc-rpi-pcf8575@0.0.1-security` . I've transferred write access to the package over to your [@xxx](https://www.npmjs.com/~xxx) user account. You should now be able to publish a new version, though you'll be unable to reuse any of the past version numbers.

Please let us know if there is anything else we can do for you. We’ll be here to help.

Thanks so much.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)
#### Post date: [16 February 2021 15:50 UTC](https://discourse.nodered.org/t/problems-with-npm-publish-why-is-my-node-spam/40229/7 "2021-02-16T15:50:39Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
