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.
github-feed-cli
Advanced tools
Github feed right at your terminal.
depandabot
events$ npm install --global github-feed-cli
If you are using npm
version 5.2+
or higher then you can use this tool with npx
too.
$ npx feed
Usage
$ feed <options>
Options
--username, -u Github username to fetch the feed [default: Your own git username]
--page, -p Page number of the results to fetch [default: 1]
--version, -v Get the current version
Examples
$ feed
$ feed --page 2
$ feed --username rocktimsaikia
$ feed --username rocktimsaikia -page 2
If you want to add new feature or improve the existing ones of github-feed-cli
, please open an issue :rocket:
read-git-user
- Reads the Github username and email from .gitconfig
:wrench: and returns it as a json object
MIT © Rocktim Saikia
FAQs
Github feed right at your terminal
The npm package github-feed-cli receives a total of 2 weekly downloads. As such, github-feed-cli popularity was classified as not popular.
We found that github-feed-cli 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.