Skip to content

All integrations

Connect npm to ShipVitals

Daily downloads per package

AvailableNothing to authorise · about 1 minute

Connect npm

What it reads

There's nothing to grant: it reads what is public.

Read-only: ShipVitals can't change anything at npm.

What ShipVitals keeps: The package names you list.

Every connector's scopes, on one page

How to connect

About 1 minute.

How to revoke

Removing the connection in ShipVitals deletes the stored key at once.

What it powers

Dashboard tabs: Usage.

Figures it fills

  • npm downloads

Sync

  • Free: Daily
  • Indie: Hourly
  • Studio: Every 15 minutes
  • Agency: Every 15 minutes

Troubleshooting

Each error a connection can hit, and its fix. The connection's health page names the one it hit.

Access refused
npm no longer accepts what ShipVitals signs in with. Create a new key, or connect again, and replace it in the connection.
A permission is missing
What ShipVitals has can't read everything it needs. Add the permissions under What it reads, or create a new key with them, and test again.
Access removed
ShipVitals' access was removed in npm. Connect it again; the history it brought in is kept.
Rate-limited
npm asked ShipVitals to slow down. Nothing to do: the sync carries on by itself and catches up.
Quota reached
The account used up a npm quota. The sync resumes when the quota resets.
Not found
Something the connection reads is gone from npm: renamed, moved or removed. Review the connection's resources, or connect again.
npm is unavailable
npm is having trouble on its side. Check its status page; ShipVitals retries by itself.
Couldn't reach npm
The request didn't get through. ShipVitals retries by itself; if it keeps failing, check that npm is reachable.
An answer ShipVitals didn't expect
npm answered in a shape ShipVitals didn't expect, usually after a change on its side. We're told, and the data you have is kept.
A setting doesn't work
A field in the connection doesn't work with npm. Check it against How to connect, and test again.

Docs