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/registry

v6.0.0

Published

The geocode-first record-matching application: resolve messy contact/organization records into canonical, geocoded entities (block → score → cluster) and export them as GeoJSON for spatial analysis. The clinic-funding use case mailwoman was built for.

Readme

@mailwoman/registry

Geocode-first record-matching application — the high-level entry point that runs the full block → score → cluster pipeline over ingested records and returns canonical entities ready for export.

This is the clinic-funding use case Mailwoman was built for, standing on a calibrated, label-free matcher.

import { resolveEntities, ingestRows, toGeoJSON } from "@mailwoman/registry";

// 1. Ingest — CSV/array → normalized SourceRecords
const records = ingestRows(rows, {
  mapping: { name: "Provider Name", address: "Street Address", city: "City", ... },
});

// 2. Resolve — block → score → cluster with geo-first defaults
const entities = resolveEntities(records, {
  geocodeAddress: async (row) => ({ lat: 30.2672, lon: -97.7431 }),
});

// 3. Export — GeoJSON for QGIS
const fc = toGeoJSON(entities);
// → FeatureCollection with Point features + entity properties

The full pipeline

CSV / SQLite → ingestRows → SourceRecord[] → resolveEntities → ResolvedEntity[]
                                                                    ↓
                                                               toGeoJSON()
                                                                    ↓
                                                            GeoJSON → QGIS

API

// Ingest — parse CSV / map columns → normalized records
import { ingestRows, parseCsv, inferMapping } from "@mailwoman/registry"
// {
//   ingestRows(rows, opts): SourceRecord[]
//   parseCsv(csvText): string[][]
//   inferMapping(headers): ColumnMapping
// }

// Resolve — run the full matcher pipeline
import { resolveEntities } from "@mailwoman/registry"
// resolveEntities(records, config): ResolvedEntity[]
// Config: { geocodeAddress?, scorer?, blockingKeys?, threshold?, discriminators? }

// Export — GeoJSON, MapLibre HTML, reconciliation reports
import { toGeoJSON, toMapHTML, reconcile } from "@mailwoman/registry"

// Learned scorer — pre-trained GBT for single-dataset dedup
import { dedupGbtEnUs } from "@mailwoman/registry"

Default configuration

resolveEntities ships with sensible defaults:

  • Blocking keys: geo-cell (H3) + canonical address + phone + email
  • Scoring model: Fellegi-Sunter with label-free EM, term frequency adjustment
  • Learned scorer: optional GBT for single-dataset dedup (opt-in via scorer)
  • Threshold: 0.5 (configurable precision/recall knob)

CLI

The mailwoman CLI exposes registry as a command:

# Multi-source entity resolution
mailwoman registry --sources config.json --out entities.geojson

# Cross-dataset reconciliation
mailwoman registry --sources tx-nppes.json --reconcile tx-fcc.json

Related

License

AGPL-3.0-only