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

@beinfi/sdk

v0.3.0

Published

Infi SDK — email-code auth and revenue infrastructure for technical founders

Readme

@beinfi/sdk

Email-code auth and revenue infrastructure for technical founders. One SDK for login, usage metering and billing.

npm install @beinfi/sdk

Quick start

import { Infi } from "@beinfi/sdk";

const infi = new Infi({
  secretKey: process.env.INFI_SECRET_KEY!, // sk_test_... / sk_live_...
  baseUrl: process.env.INFI_API_URL,       // optional, defaults to https://api.beinfi.com
});

Passing just a key uses the production defaults:

const infi = new Infi(process.env.INFI_SECRET_KEY!);

Email-code login (public — no secret key needed)

// 1. send the 6-digit code
await infi.sendEmailCode({ slug: "your-app", email: "[email protected]", redirectTo: "/callback" });

// 2. verify it → get the redirect URL carrying a single-use auth code
const { redirectUrl } = await infi.verifyEmailCode({ slug: "your-app", email: "[email protected]", code: "123456" });
// navigate the browser to redirectUrl to finish the hosted flow

Exchange the auth code (server-side — secret key)

const result = await infi.exchangeCode(code);         // from ?code= on your callback
// or straight from a request:
const result = await infi.exchangeCodeFromRequest({ url: req.url });

result.identity; // AppIdentity
result.customer; // { id, externalId, email, ... }
result.session;  // { token, expiresAt } | undefined

Metering (server-side — secret key)

await infi.track({ customerId: "cus_123", meter: "tokens", value: "1200" });

await infi.trackBatch([
  { customerId: "cus_123", meter: "tokens", value: "1200" },
  { customerId: "cus_123", meter: "api_call", value: "1" },
]);

React

import { InfiLogin } from "@beinfi/sdk/react";

<InfiLogin slug="your-app" redirectTo="/callback" />;

Next.js

For App Router route handlers (Login, Callback, Usage), use @beinfi/nextjs.

Config

| Option | Default | Notes | | --- | --- | --- | | secretKey | — | sk_... for server-side calls (exchange, metering). Public login needs no key. | | baseUrl | https://api.beinfi.com | Infi API base URL. | | authBaseUrl | https://api.beinfi.com | Hosted login base URL (served off the API host). |

Types are generated from the Infi OpenAPI spec, so requests and responses stay in sync with the API.

MIT © Infi