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

lewsearch

v0.1.0

Published

Query a calibrated panel of synthetic respondents from your code — the official Lewsearch (Lewis) SDK.

Readme

lewsearch

Poll a calibrated panel of synthetic respondents from your code. Ask any question, get back how a population actually splits — with an honest confidence read and panel composition. Benchmarked against Pew, Gallup & UT/TPP (~7.5 pp MAE on structured items).

npm install lewsearch

Quick start

import { Lewsearch } from "lewsearch";

const ls = new Lewsearch({ apiKey: process.env.LEWSEARCH_API_KEY! });

const res = await ls.poll({
  question: "Would you switch brands at $4.99?",
  options: ["Definitely", "Probably", "Probably not", "No"],
  audience: { market: "national_us", n: 500 },
});

console.log(res.summary);
// "Among US adults (n=500), Probably leads at 38% (vs No 27%...). Directional read."
console.log(res.distribution);
// [ { option: "Probably", pct: 38.0, count: 190 }, ... ]
console.log(res.confidence);        // { score: 0.74, label: "Directional", tier: "amber" }
console.log(res.panel_composition); // { n_real: 500, n_synthetic: 0, n_total: 500, ... }

res.summary is a ready-to-print sentence — great for logging or handing straight to a coding agent. Everything else (res.distribution, res.confidence, res.panel_composition) is the structured detail.

Get an API key at https://lewsearch.com/developers.

Calibrated vs. free-form

  • Pass 2–6 options → a calibrated multiple-choice read (the trustworthy path; benchmarked against Pew/Gallup).
  • Omit options → an uncalibrated free-form read (directional only, no numeric accuracy claim).

Always check res.confidence.tier before leaning on a number.

Example: a price demand curve

const prices = [2.99, 3.99, 4.99, 5.99];
for (const price of prices) {
  const res = await ls.poll({
    question: "Would you buy this at $" + price + "?",
    options: ["Yes", "No"],
    audience: { market: "national_us", n: 1000 },
  });
  const yes = res.distribution.find((d) => d.option === "Yes")?.pct ?? 0;
  console.log("$" + price + " -> " + yes + "% would buy");
}

API

new Lewsearch({ apiKey, baseUrl?, timeout? })

  • apiKey — your sk-lew-... key (required).
  • baseUrl — defaults to https://lewsearch.com/api/v1.
  • timeout — ms, default 60000.

ls.poll(params) → Promise<PollResult>

  • question: string (required)
  • options?: string[] — 2–6 for calibrated MC
  • audience?: { market?: string; n?: number } — e.g. market: "national_us" | "columbus" | "texas"; n is clamped to your plan's per-query max
  • requestId?: string — idempotency key (a retried request bills once)

Errors throw LewsearchError with .status and .code (UNAUTHORIZED, FORBIDDEN, RATE_LIMITED, TIMEOUT, API_ERROR, …).

Billing

Metered by respondents queried against your plan's monthly pool. res.usage shows respondents_billed, month_used, and month_limit. Enterprise deployments run on dedicated inference with no per-call cost. Full docs: https://lewsearch.com/api-docs.


Made by Lewsearch · synthetic respondents are estimates, not guarantees.