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.
is-github-user-or-org
Advanced tools
Determines whether a GitHub profile is a User or an Organization
$ npm install --save is-github-user-or-org
You also need to get a GitHub application token: https://github.com/settings/tokens. Provide it in the CLI or set it as $GITHUB_TOKEN
somewhere in your bash_profile.
const isGithubUserOrOrg = require('is-github-user-or-org')
isGithubUserOrOrg('RichardLitt')
//=> 'User'
Type: string
The user or organization you want to check the type of
Type: token
The GitHub personal access token.
Type: string
The GitHub enterprise endpoint.
$ npm install --global is-github-user-or-org
$ is-github-user-or-org --help
Usage
$ is-github-user-or-org <input>
Options
-t, --token A token
-e, --endpoint A GitHub endpoint (for Enterprise)
Examples
$ get-github-user RichardLitt
User
$ get-github-user OpenSourceDesign
Organization
MIT © 2017 Richard Littauer
FAQs
Determines whether a GitHub profile is a User or an Organization
We found that is-github-user-or-org 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.