SocketDev / SocketDev/socket-cli
429 too many requests with clean npm install on free plan
Open
Nobody has claimed this yet.
question
- Dominant language
- TypeScript
- Stars
- 317
- Forks
- 65
- Avg merge
- 1h 26m
- Merged PRs (30d)
- 30
Description
I got rate-limited for trying to use the cli to install all packages from my package.json:
⠏ Looking up data for 760 packages(node:67363) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 31 abort listeners added to [AbortSignal]. MaxListeners is 30. Use events.setMaxListeners() to increase limit
(Use `node --trace-warnings ...` to show where the warning was created)
⠹ npm error Socket API POST request failed (429): Too Many Requests
npm error A complete log of this run can be found in: /path/to/.npm/_logs/2025-11-28T13_17_29_504Z-debug-0.log
Seems very unusual that such a basic npm feature doesn't work. I'm on a free plan, could that be it?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the CLI install with a package.json containing many packages and inspect the request path associated with the reported Socket API POST 429. Compare the behavior with a smaller install and the warning output; done means a clean install of the reported package set does not unexpectedly hit rate limits on the free plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100