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

@skink/sdk

v0.1.0

Published

Official server-side Node.js client for the skink email verification API

Readme

@skink/sdk — Node.js

Official server-side client for the skink email verification API.

⚠️ Server-side only — never use this in a browser

Your API key is a secret credential, same as a database password. This client throws if it detects a browser environment, but that's a backstop, not the plan — never ship your key in frontend JavaScript, a mobile app bundle, or any code a user's device can inspect. Anyone who reads it can spend your credits and see verification activity on your account. Load it from a server-side environment variable and call skink from your own backend; have your frontend call your backend, not skink directly.

If a key is ever exposed, revoke it immediately from the dashboard (/keys) and issue a new one.

Install

Copy this directory into your project, or npm install it once published. Requires Node 18+ (uses the built-in fetch).

Usage

import { SkinkClient } from "@skink/sdk";

const skink = new SkinkClient(process.env.SKINK_API_KEY);

const result = await skink.verify("[email protected]");
console.log(result.status, result.confidence, result.signals.reasons);

const job = await skink.bulkCreate({ emails: ["[email protected]", "[email protected]"] });
const status = await skink.bulkStatus(job.job_id);

API

  • new SkinkClient(apiKey, { baseUrl?, timeoutMs? })
  • verify(email, { timeoutMs?, idempotencyKey? })
  • uploadFile(csvBufferOrString) → { file_id }
  • bulkCreate({ emails? , fileId? }, callbackUrl?)
  • bulkList()
  • bulkStatus(jobId)
  • bulkResults(jobId)
  • reportBounce(email, outcome, { verifiedAt? })

All methods throw SkinkError (.status, .code, .message) on a non-2xx response.