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

@frogbotai/plugin-api-keys

v0.20.0

Published

Multiple named API keys for FrogBot.

Readme

@frogbotai/plugin-api-keys

Add multiple named, independently revocable API keys to a FrogBot application.

import { apiKeysPlugin } from '@frogbotai/plugin-api-keys';
import { buildConfig } from 'frogbot';

export default buildConfig({
  secret: process.env.FROGBOT_SECRET!,
  db: databaseAdapter,
  collections: [{ slug: 'users', auth: true, fields: [] }],
  plugins: [apiKeysPlugin()],
});

The plugin adds an api-keys collection, owner-scoped management endpoints, API-key authentication, and default admin controls. frogbot dev generates the admin import map before starting, so the key-creation controls appear on the first load. Create a key in the API Keys admin collection, then authenticate requests with either header:

Authorization: Bearer fbt_...
X-API-Key: fbt_...

Plaintext keys are returned only when created. The collection stores SHA-256 hashes and supports multiple independently revoked keys per user.

With AI configured, usage rows include an optional apiKey relationship to the authenticating key. Cookie-authenticated requests omit it, and the relationship follows collectionSlug.

Build and start-only workflows must run frogbot generate:importmap after adding the plugin. Add it as a prebuild step when CI invokes next build directly. If the server console suggests payload generate:importmap, run frogbot generate:importmap instead, or restart frogbot dev.

apiKeysPlugin({
  authCollection: 'accounts',
  collectionSlug: 'credentials',
  tokenPrefix: 'acme',
  headerNames: ['x-service-key'],
  collection: {
    admin: { group: 'Security' },
    fields: [{ name: 'environment', type: 'text' }],
  },
});

Collection overrides merge with the generated fields, access, endpoints, hooks, admin components, and transforms applied by other plugins. The manager uses Payload controls without plugin CSS, so global admin styles continue to apply.

The plugin has no role system of its own. Keys are owner-scoped, and budget fields are read-only. To layer roles on top, install @frogbotai/plugin-roles, list it after apiKeysPlugin(), and pass policyAccess and canRevokeAnyKey:

import { allow, hasRole } from '@frogbotai/plugin-roles';

apiKeysPlugin({
  policyAccess: allow('admin'),
  canRevokeAnyKey: (req) => hasRole(req, 'admin', 'support'),
  collection: {
    access: {
      read: allow('auditor', 'support', { role: 'member', own: 'owner' }),
      update: allow('support', { role: 'member', own: 'owner' }),
    },
  },
});