Every check / package-token-exposed
Is a token that can publish code in your name readable on your site?
On a domain you have proved is yours, we ask for /.npmrc, the settings file npm reads, and look for an _authToken in it.
How it decides
The check speaks up when there is one, and never records it.
Why it matters
That token publishes packages under your account.
In more detail
If your business publishes any, somebody could release a version containing whatever they like, and every project that installs it would run that code. It needs revoking, and the publish history checking for releases you did not make.
Who fixes it, and where it runs
- Who usually fixes it
- Whoever built your site
- Which plan runs it
- The Business plan
- Proof you own the site
- Needed. It asks your server for things an ordinary visitor never requests, so it waits until you prove the domain is yours.
More about this check
- Who it is about
- An intruder
- Listed under
- Things that should not be public
- The standard
- Its name in a report
package-token-exposed
See what the free scan finds
The free scan runs 62 checks on any address, and this is not one of them: it runs on the Business plan, once you prove the domain is yours.