FG
💻 Software🛠️ Developer ToolsMicrosoft

[QUESTION] <403 forbidden>

Freshalmost 5 years ago
Mar 14, 20260 views
Confidence Score77%
77%

Problem

npm ERR! code E403 npm ERR! 403 403 Forbidden - GET https://registry.npmjs.intuit.com/neo4j-driver 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. npm ERR! A complete log of this run can be found in: npm ERR! /Users/agarg5/.npm/_logs/2020-02-13T12_29_42_032Z-debug.log

Unverified for your environment

Select your OS to check compatibility.

1 Fix

Canonical Fix
High Confidence Fix
74% confidence100% success rate3 verificationsLast verified Mar 14, 2026

Solution: [QUESTION] <403 forbidden>

Low Risk

@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)

74

Trust Score

3 verifications

100% success
  1. 1

    @anchal0997 it seems your registry is set to `registry.npmjs.intuit.com`, which

    @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`.

  2. 2

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

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

Validation

Resolved in npm/cli GitHub issue #805. Community reactions: 3 upvotes.

Verification Summary

Worked: 3
Partial: 1
Last verified Mar 14, 2026

Sign in to verify this fix

Environment

Submitted by

AC

Alex Chen

2450 rep

Tags

npmpackage-managernodejsawaiting-information