Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
@sanity/timed-out
Advanced tools
Emit `ETIMEDOUT` or `ESOCKETTIMEDOUT` when ClientRequest is hanged
Timeout HTTP/HTTPS requests
Emit Error object with code
property equal ETIMEDOUT
or ESOCKETTIMEDOUT
when ClientRequest is hanged.
var get = require('http').get;
var timeout = require('timed-out');
var req = get('http://www.google.ru');
timeout(req, 2000); // Set 2 seconds limit
Required
Type: ClientRequest
The request to watch on.
Required
Type: number
or object
Time in milliseconds to wait for connect
event on socket and also time to wait on inactive socket.
Or you can pass Object with following fields:
connect
- time to wait for connectionsocket
- time to wait for activity on socketMIT © Vsevolod Strukchinsky
FAQs
Emit `ETIMEDOUT` or `ESOCKETTIMEDOUT` when ClientRequest is hanged
The npm package @sanity/timed-out receives a total of 55,350 weekly downloads. As such, @sanity/timed-out popularity was classified as popular.
We found that @sanity/timed-out demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 14 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.