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

@mailwoman/nominatim

v7.8.1

Published

Nominatim drop-in — a Nominatim-compatible HTTP geocoding API (search / reverse / lookup / status) over the Mailwoman engine. Run it with `npx @mailwoman/nominatim serve`.

Readme

@mailwoman/nominatim

A Nominatim-compatible HTTP geocoding API over the Mailwoman engine. Point an existing Nominatim client at it and forward + reverse geocoding work — no PostgreSQL, no osm2pgsql import.

npx @mailwoman/nominatim serve --port 8080 --candidate-db <gazetteer-or-bundle>
from geopy.geocoders import Nominatim

geo = Nominatim(domain="localhost:8080", scheme="http")
geo.geocode("1600 Pennsylvania Ave NW, Washington DC", addressdetails=True)
geo.reverse((38.8977, -77.0365))

Endpoints

| Endpoint | Nominatim contract | Status | | --------------- | ------------------------------------------------------------- | ------- | | / | HTML landing page (endpoint index + example queries) | ✓ | | /search | free-text q + structured forward geocoding | ✓ | | /reverse | lat/lon → nearest address (WofReverseGeocoder PIP) | ✓ | | /status | health + data version | ✓ | | /lookup | resolve known place ids | planned | | /openapi.json | emitted OpenAPI 3.1 document for search/reverse/lookup/status | ✓ |

Library use

The package is engine-agnostic — embed it in your own server:

import { serveNode } from "@mailwoman/api-kit"
import { createNominatimApp, type NominatimEngine } from "@mailwoman/nominatim"

const engine: NominatimEngine = {/* search, reverse, lookup, status — backed by your Mailwoman pipeline */}
const app = createNominatimApp(engine)
serveNode({ fetch: app.fetch, port: 8080, hostname: "0.0.0.0" })

CORS

Browser-embedded geocoder clients call this cross-origin, so the server sends permissive CORS by default — Access-Control-Allow-Origin: * and a 204 answer to preflight OPTIONS. Behind a reverse proxy that already sets the headers, turn it off with --no-cors (or createNominatimApp(engine, { cors: false })).

Annotations

Every result carries an OpenCage-style annotations block — coordinate formats (DMS, MGRS, geohash, Maidenhead, Mercator), qibla bearing, sun times, country flag, calling code, and currency, plus the IANA timezone, UN/LOCODE, and EU NUTS codes when their data bundles are present. Plain Nominatim returns none of these.

Status

Shipped. /search and /reverse resolve over the live engine and return the enriched block; /lookup is not yet implemented (returns 501). addressdetails goes down to the house number and road when the query carries them — 1600 Pennsylvania Avenue NW, Washington, DC 20500 resolves to the rooftop (38.897, -77.037) with house_number, road, city, state, postcode, and country_code.

For autocomplete / type-ahead, see the companion @mailwoman/photon.