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

gridpin

v0.8.0

Published

Offline geocoder: addresses to coordinates and back from one local file per country, no API key, no query leaves the machine

Readme

gridpin for Node.js

Offline geocoder: an address to coordinates and back, from one local file per country (a "sheet"). No API key, no rate limit, no query leaves the machine. The same engine as the gridpin CLI, Python package, R package and DuckDB extension, through its C interface.

const { Geocoder, sheets } = require('gridpin');

const sheet = await sheets.fetch('us');          // once: download, check size and SHA-256 against the signed release
const g = new Geocoder(sheet);
g.geocode('1600 Pennsylvania Ave NW, Washington, DC', { k: 1 });
// [{ lat: 38.8976751, lon: -77.036547, precision: 'house', street: 'PENNSYLVANIA Avenue Northwest',
//    housenumber: '1600', commune: 'Washington', postcode: '20500', confidence: 0.95, weak: false, ... }]
g.geocodeMany(['10 Downing St', null, '350 5th Ave, New York']);   // one list per row, input order kept
g.reverse(38.8977, -77.0365);
g.close();
  • weak: true marks an answer the engine itself says needs a check before use (city level, low confidence, or a fuzzy street with middling confidence). An exact house on an exact street is never weak.
  • Sheets live where the CLI and gridpin-mcp keep them: GRIDPIN_HOME, else $XDG_CACHE_HOME/gridpin, else ~/.cache/gridpin. sheets.list(), sheets.where('us'), sheets.verify('us'); GRIDPIN_OFFLINE=1 forbids downloads.
  • geocodeMany runs on the calling thread: for large batches, use a worker thread.

Countries, data sources and licenses: https://gridpin.dev. Engine: Apache-2.0. Sheet data: OpenStreetMap contributors (ODbL), Overture Maps and national open address sources.