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

@banata-auth/sdk

v0.2.0

Published

Server-side SDK for the Banata Auth platform — manage users, organizations, SSO, RBAC, webhooks, and more

Readme

@banata-auth/sdk

Dashboard-first Banata Auth API client.

This package is the public product surface that should feel closest to WorkOS:

  • it authenticates with an API key
  • it talks to Banata HTTP endpoints
  • it does not access your database directly

Start in the Banata dashboard: create a project, issue a project-scoped API key, then initialize the SDK with that key. The API key is the project selector. You should not need to pass a separate projectId for the normal managed-service flow.

Installation

npm install @banata-auth/sdk

Usage

import { BanataAuth } from "@banata-auth/sdk";

const banata = new BanataAuth({
  apiKey: process.env.BANATA_AUTH_API_KEY!,
  baseUrl: process.env.BANATA_AUTH_BASE_URL!,
});

const users = await banata.users.listUsers({ limit: 20 });

await banata.rbac.updateRole({
  id: "role_123",
  permissions: ["employee.read", "leave.approve"],
});

Resources

  • users
  • organizations
  • sso
  • directories
  • webhooks
  • rbac
  • projects
  • vault
  • auditLogs
  • events
  • emails
  • domains
  • portal
  • apiKeys

Notes

  • Pass baseUrl explicitly. This is the Banata API origin your app should call.
  • For self-hosting, use the repo's self-hosting docs instead of this package README.