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.
@chirper/node
Advanced tools
Rinse, React, repeat. A boilerplate to build a React component library.
To start your own React component library, clone this repository and start your own Git journey!
$ git clone https://github.com/cwlsn/rinse-react cool-name
$ cd cool-name
$ rm -rf .git
$ git init
You can easily develop and interact with your components by using Storybook. To run the local server, simply run:
$ npm i
$ npm run storybook
Navigate to http://localhost:9001 to view your stories. They should automatically update as you develop.
Storybook will pick up any story from the stories.js
file in a component folder.
Rinse is currently using the latest technology available, so you may need to update your Node versions to latest to accomodate Babel 7 and Webpack 4.
FAQs
Unknown package
The npm package @chirper/node receives a total of 2 weekly downloads. As such, @chirper/node popularity was classified as not popular.
We found that @chirper/node demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 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.