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

@pikku/addon-admin

v0.12.15

Published

Admin addon for Pikku — the user directory, roles and scopes, credentials and the audit trail, as ordinary RPCs

Readme

@pikku/addon-admin

Administration for a Pikku application, as ordinary namespaced RPCs: the user directory, roles and scopes, credentials, and the audit trail.

Separate from @pikku/addon-console on purpose. The console addon exists to be served alongside a running dev server — it reads generated metadata, project source and knowledge notes from disk. This one touches nothing but the services your application already has, so it can be wired into a deployed serverless unit and called from your own admin screens without the console anywhere in sight.

Install

npm install @pikku/addon-admin
import { wireAddon } from '#pikku/pikku-types.gen.js'

wireAddon({
  name: 'admin',
  package: '@pikku/addon-admin',
  expose: true,
  globalCredentials:
    'administering credentials means setting and clearing any of them, for any user, so it cannot be scoped to a declared set',
})

globalCredentials is required for the admin:credential* functions. An addon is otherwise handed a CredentialService scoped to the credentials it declares itself, and this one declares none — so without the opt-out every credential call finds nothing. Leave it off if you only want users, scopes and audits.

Every function carries its own admin:* scope, so a role can grant reading the directory without granting the ability to ban anyone. Note the absence of scopes on wireAddon: addon scopes are required in addition to a function's own, so declaring admin there would force the umbrella grant on every caller.

admin:users:* needs better-auth wired, and banning additionally needs its pikkuBan() plugin from @pikku/better-auth for the columns to exist:

import { pikkuBan } from '@pikku/better-auth'

betterAuth({ plugins: [pikkuBan()] })

better-auth's own admin() plugin is neither needed nor wanted here. These functions work through the internal adapter, and each is already gated by its own admin:* scope — admin() would only add a second check against a role column that has to be kept in step with the scopes it duplicates.

admin:audit:read needs an audit sink that can be read back. Both report their absence rather than failing.

Docs

https://pikku.dev/docs