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 🙏

© 2026 – Pkg Stats / Ryan Hefner

importio-signer-heroku

v0.0.1

Published

a heroku app to sign client queries to import.io

Readme

importio-signer-heroku

A simple node.js app, deployable to Heroku, for signing import.io queries for your zumbi clients out there.

Rationale

If you use Import.IO for scraping (and you should!), you must use a signing server for signing(!) your clients queries. In other words, its a bad idea to let your api key lay open on the source of your super index.html or even on a hyper uglyfied javascript compiled from typescript compiled from Visual Basic 2013 Web Express or something like that.

That being said, you should:

Step-by-step

git clone https://github.com/weltonrodrigo/importio-signer-heroku.git
cd importio-signer-heroku
heroku login
heroku create
heroku push master

heroku config:set IMPORTIO_USERGUID=21fe0000-0000-0000-0000-af4300007640
heroku config:set IMPORTIO_APIKEY=your_long_api_key_string

heroku ps:scale web=1

On your code:


this.importio.init({
             "auth": "http://adjective-noum-9999.herokuapp.com/",
             "host": "import.io"
});

References

This doc explains how to use signed queries: http://docs.import.io/35/signedserver.html

A word of caution

Please be warned that you are the sole responsible for securing your keys and you should not blame anyone but you if something bad happen with them.

Keys being stolen from heroku via 0-day exploits or accidentaly being commited on a public GitHub repo are examples of that.