npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

github-keys

v1.0.1

Published

find the public keys of a given github user

Downloads

5

Readme

github-keys

github-keys is a simple module that finds the public keys of a given Github user. Its code is based on a private function in substack/cipherhub, however github-keys maintains a streaming API and doesn’t filter the returned keys.

Build status

Install

$ npm install [-g] github-keys

Usage

var keys = require('github-keys')
var through = require('through2')

keys('alice').pipe(through(
  function (key, enc, next) {
    console.log(key.toString())
    next()
  }
))

w/callbacks

Sometimes you just want all the keys in an array, so github-keys provides an alternate endpoint to facilitate that use-case.

var keys = require('github-keys/all')

keys('alice', function (err, array) {
  console.log(array)
})
Running the usage examples

To run either of these examples in node or the browser, use the following commands:

# node
$ npm run example
$ npm run example-all

# browser, obviously
$ npm run example-browser
$ npm run example-all-browser

Because Github doesn’t support CORS for the /{user}.keys endpoint, github-keys needs to go through a reverse proxy in order to work in the browser. This is easily configured, however, with the browserify transform, envify:

$ CORS_PROXY='http://cors.proxy.com/' browserify -t envify program.js > bundle.js

Command-line usage

If you install github-keys with the -g flag, you can access the command-line version:

$ github-keys {username}

License

MIT