
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
@aboveyou00/github
Advanced tools
A Node.js wrapper for GitHub API.
Install via npm.
npm install github
or install via git clone:
git clone https://github.com/octokit/node-github
cd node-github
npm install
Client API: octokit.github.io/node-github GitHub API: developer.github.com/v3
Get all followers for user "defunkt":
var GitHubApi = require('github')
var github = new GitHubApi({
// optional
debug: true,
Promise: require('bluebird'),
timeout: 5000,
host: 'github.my-GHE-enabled-company.com', // should be api.github.com for GitHub
pathPrefix: '/api/v3', // for some GHEs; none for GitHub
protocol: 'https',
port: 9898,
proxy: '<proxyUrl>',
ca: 'whatever',
headers: {
'accept': 'application/vnd.github.something-custom',
'cookie': 'something custom',
'user-agent': 'something custom'
},
requestMedia: 'application/vnd.github.something-custom',
followRedirects: false, // default: true; there's currently an issue with non-get redirects, so allow disabling follow-redirects
rejectUnauthorized: false, // default: true
family: 6
})
// TODO: optional authentication here depending on desired endpoints. See below in README.
github.users.getFollowingForUser({
// optional
// headers: {
// "cookie": "blahblah"
// },
username: 'defunkt'
}, function (err, res) {
if (err) throw err
console.log(JSON.stringify(res))
})
There are a few pagination-related methods:
hasNextPage(link)
hasPreviousPage(link)
hasFirstPage(link)
hasLastPage(link)
getNextPage(link, headers, callback)
getPreviousPage(link, headers, callback)
getFirstPage(link, headers, callback)
getLastPage(link, headers, callback)
NOTE: link is the response object or the contents of the Link header
See here and here for examples.
Most GitHub API calls don't require authentication. As a rule of thumb: If you can see the information by visiting the site without being logged in, you don't have to be authenticated to retrieve the same information through the API. Of course calls, which change data or read sensitive information have to be authenticated.
You need the GitHub user name and the API key for authentication. The API key can be found in the user's Account Settings.
// basic
github.authenticate({
type: 'basic',
username: process.env.USERNAME,
password: process.env.PASSWORD
})
// oauth
github.authenticate({
type: 'oauth',
token: process.env.AUTH_TOKEN
})
// oauth key/secret (to get a token)
github.authenticate({
type: 'oauth',
key: process.env.CLIENT_ID,
secret: process.env.CLIENT_SECRET
})
// user token
github.authenticate({
type: 'token',
token: 'userToken'
})
// integration (jwt)
github.authenticate({
type: 'integration',
token: 'jwt'
})
// ~/.netrc
github.authenticate({
type: 'netrc'
})
Note: authenticate is synchronous because it only stores the
credentials for the next request.
X-GitHub-OTP header with the one-time-password you get on your token device.github.authorization.create({
scopes: ['user', 'public_repo', 'repo', 'repo:status', 'gist'],
note: 'what this auth is for',
note_url: 'http://url-to-this-auth-app',
headers: {
'X-GitHub-OTP': 'two-factor-code'
}
}, function (err, res) {
if (err) throw err
if (res.token) {
// save and use res.token as in the Oauth process above from now on
}
})
Create test auth file for running tests/examples.
$ > testAuth.json
{
"token": "<TOKEN>"
}
For using bluebird, see here. For using Q, see here.
Run all tests
$ npm test
Or run a specific test
$ npm test test/issuesTest.js
Accept headers for the preview APIs should be taken care of behind the scenes, but in the event a preview endpoint isn't working, see here for an example on how to add the required custom accept header.
For updates on endpoints under preview, see https://developer.github.com/changes/.
| Preview API | Accept header val |
|---|---|
| Blocking Users | application/vnd.github.giant-sentry-fist-preview+json |
| Codes of Conduct | application/vnd.github.scarlet-witch-preview+json |
| Commit Search | application/vnd.github.cloak-preview+json |
| Community | application/vnd.github.black-panther-preview+json |
| Deployment | application/vnd.github.ant-man-preview+json |
| Git signing | application/vnd.github.cryptographer-preview |
| Imports | application/vnd.github.barred-rock-preview |
| Integrations | application/vnd.github.machine-man-preview |
| License | application/vnd.github.drax-preview+json |
| Marketplace | application/vnd.github.valkyrie-preview+json |
| Migrations | application/vnd.github.wyandotte-preview+json |
| Nested Teams | application/vnd.github.hellcat-preview+json |
| Pages | application/vnd.github.mister-fantastic-preview |
| Pre-receive | application/vnd.github.eye-scream-preview |
| Projects | application/vnd.github.inertia-preview+json |
| Pull Request Squash | application/vnd.github.polaris-preview |
| Reactions | application/vnd.github.squirrel-girl-preview |
| Review Requests | application/vnd.github.thor-preview+json |
| Star Creation Timestamp | application/vnd.github.v3.star+json |
| Timeline | application/vnd.github.mockingbird-preview |
| Topics | application/vnd.github.mercy-preview+json |
To update the apidoc for github pages:
$ npm install apidoc -g
$ apidoc -i doc/ -o apidoc/
Just a reminder, since an ad-hoc filter was added to the apidoc, don't overwrite index.html, main.js.
MIT license. See the LICENSE file for details.
FAQs
NodeJS wrapper for the GitHub API
We found that @aboveyou00/github 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
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.