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

@signalsapi/client

v0.2.0

Published

Keyless JavaScript client for the public SignalsAPI reads — hiring-requisition search and the data-provenance statement

Readme

@signalsapi/client (JavaScript)

Keyless JavaScript client for the two public SignalsAPI reads. No API key, no dependencies, no build step — install it and the next line returns live data.

Requires Node 18+ (global fetch). ESM only.

Install

npm i @signalsapi/client

The Python client of the same two reads is pip install signalsapi. This one is scoped because npm's name-similarity filter permanently rejects the unscoped signalsapi — it normalizes onto signals-api, an unrelated package published in 2016.

Use

import { compliance, reqsSearch } from "@signalsapi/client";

// The data-provenance guarantee — what this plane sources, and what it never serves.
const statement = await compliance();
console.log(statement.guarantee[0]);

// Who is hiring for {role, geo}. Real rows, no credentials.
const result = await reqsSearch({ role: "staff engineer", geo: "United States", limit: 5 });
for (const company of result.companies) {
  console.log(company.company_id, company.pulse.open_req_count.value);
}

Both calls return the response JSON verbatim — this client transcribes no response models, so what the API returns is what you get. Any non-2xx throws.

API

| Function | Endpoint | Parameters | |---|---|---| | compliance() | GET /compliance | — | | reqsSearch() | GET /sandbox/reqs/search | role, geo, since, limit (all optional) |

  • role — full-text query over the raw posting title; every word must match.
  • geo — country name, e.g. "United States". A country that cannot resolve is a 422.
  • since — ISO-8601 lower bound on when a req was first seen, passed through as written.
  • limit — companies per page, capped by the sandbox demo ceiling.

Both accept baseUrl and timeoutMs in the same options object. There is no paging: a non-null next_cursor in the response says the corpus continues past what a keyless call may read, and walking it needs a key — see https://docs.signalsapi.com/.

Base URL

https://jobsapi.signalsapi.com/api/v1 — the gateway vhost, and the only base that serves these routes publicly. api.signalsapi.com and the apex 404 them; ss.signalsapi.com answers 401 before the API is reached.

Scope

Two reads, deliberately. This is the surface an evaluator can call inside one conversation without signing up; the paid contract is a different, key-gated client. Keeping this one schema-free is what bounds the cost of maintaining it by hand (signalsapi-3791/-4173).

MIT licensed.