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.
universal-websocket-client
Advanced tools
Use the same WebSocket client code in a browser or Node.js for isomorphic apps
Uses the native WebSocket client code in a browser and the ws package client on Node.js, enabling isomorphic applications to use WebSockets. Keeps your browser build slim, by not including any of the Node WebSocket implementation.
npm install --save universal-websocket-client
var WebSocket = require('universal-websocket-client');
\\ ... use the [WebSocket client interface](https://developer.mozilla.org/en-US/docs/Web/API/WebSocket).
On the client side, you'll now need to use browserify (or Webpack or something similar) to bundle your code.
See tests/browser
and tests/node
These are end-to-end tests, that test the installed the package.
cd tests/browser/
npm install
npm test
cd tests/node/
npm install
npm test
Then visit http://localhost:8000
FAQs
Use the same WebSocket client code in a browser or Node.js for isomorphic apps
We found that universal-websocket-client demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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.