Cli: [QUESTION] <403 forbidden>

The same can happen for default registry url sometimes (randomly), for example when installing from docker container using AWS codebuild:

Step 1/6 : FROM node:10-slim
...

Step 4/6 : RUN npm install grunt -g
--
514 | ---> Running in XXXXXXX
515 | npm ERR! code E403
516 | npm ERR! 403 403 Forbidden - GET https://registry.npmjs.org/grunt
517 | npm ERR! 403 In most cases, you or one of your dependencies are requesting
518 | npm ERR! 403 a package version that is forbidden by your security policy.

Somewhat related to #622

getting the same error on heroku build

Step 16/20 : RUN npm ci && npm run production
---> Running in XXXXXXX
npm ERR! code E403
npm ERR! 403 Forbidden: [email protected]
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2020-02-17T11_17_32_964Z-debug.log

When doing npm install locally i get E429 on random packages

@anchal0997 it seems your registry is set to registry.npmjs.intuit.com, which could be set in the project's package.json(in the registry field) or in your ~/.npmrc. you might need to login to that using npm login (is it a private registry?) or remove the line about it from your ~/.npmrc.

(though right now the official registry is also giving some people 403s)

Duplicate of #836

@anton-bot this is not a duplicate. this user is not using the npm registry. note this line in their initial report:

npm ERR! 403 403 Forbidden - GET https://registry.npmjs.intuit.com/neo4j-driver

(this issue is also older, 4 days ago.)

@chee he referred to the last sentence at https://github.com/npm/cli/issues/805#issuecomment-586957436

Generally this issue is not a bug in npm but a problem with the authentication with this intuit registry.

I've got exactly same error message.
And I tried a lot of things but finally after I had removed specific folder in my project,
it could be published.
In my case, the folder might be banned for uploading...
And still I can't figure out the exact reason.

In my case, the folder might be banned for uploading

What was the name of it?

In my case, the folder might be banned for uploading

What was the name of it?

The folder contains tizen tv web application.
config.xml, index.html... etc
When I had removed tizen web application, I managed to publish.

@prozanne I'm unsure if it is ok that you shared the code with us. This might be a different issue and requires some testing on your side (which file may be problematic?).

@prozanne I'm unsure if it is ok that you shared the code with us. This might be a different issue and requires some testing on your side (which file may be problematic?).

Oh.... that's ture, I think I shouldn't have uploaded the code.
I'd better to remove it.
Anyway....
Having dug a lot, finally we've got a clue.
If bootstrap.css, socket.io libraries, tizen package file(.wgt) and image resource file(.png) are contained, I couldn't publish at all.
But when we removed all of them, it worked.

You might want to remove the first version of your comment too.

I have the same issue, how can I debug it? I am collecting and packaging only .vue files, no images. Any help is appretiated

what's the package name in package.json? @avimehenwal

Had the same issue. I was trying to publish to a scope which was not in my organization. I had a typo in the scope of my package name in my package.json.

I was having this bug too, this (probably) won't work for everyone but my problem was just that I was using an already existing pacakge.

Probably not what'll fix your problem, but it fixed mines.

same issue