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

@forinda/kickjs-auth

v5.2.1

Published

Pluggable authentication for KickJS — JWT, API key, and custom strategies

Readme

@forinda/kickjs-auth

⚠️ Deprecated — moving to BYO (bring-your-own).

The framework now ships parameterised context contributors (defineContextDecorator with paramDefaults + per-call params + .with()), which give adopters all the primitives needed to compose their own auth flow without the ergonomic loss the package previously offered.

What to do: follow the BYO Auth recipe — it composes @LoadAuthUser / @RequireRole / @Public from defineContextDecorator and defineAdapter (the same primitives this package wraps). ~200 lines of adopter code you own end-to-end, no framework upgrades silently changing your auth surface.

Background: see the Context Decorators guide for the full primitive reference.

Why? @forinda/kickjs-auth couples the framework's release cadence to a domain (auth) where every project has different requirements — custom claim mapping, custom session storage, custom CSRF rules, Passport-bridge edge cases. A BYO recipe lets each project own its auth surface; the framework owns only the primitives.


Pluggable authentication for KickJS — JWT, API key, OAuth, Session, Passport bridge — plus @Authenticated / @Public / @Roles / @Can / @CsrfExempt / @RateLimit decorators, @Policy authorization, password hashing, and CSRF auto-detection.

Install

kick add auth

Quick Example

import { bootstrap, getEnv } from '@forinda/kickjs'
import { AuthAdapter, JwtStrategy } from '@forinda/kickjs-auth'
import { modules } from './modules'

export const app = await bootstrap({
  modules,
  adapters: [
    AuthAdapter({
      strategies: [
        JwtStrategy({
          secret: getEnv('JWT_SECRET'),
          mapPayload: (p) => ({ id: p.sub, email: p.email, roles: p.roles ?? ['user'] }),
        }),
      ],
      defaultPolicy: 'protected',
    }),
  ],
})

Decorate routes:

import { Controller, Get, Delete, type RequestContext } from '@forinda/kickjs'
import { Public, Roles } from '@forinda/kickjs-auth'

@Controller()
class UserController {
  @Get('/me')
  me(ctx: RequestContext) {
    return ctx.json({ user: ctx.user })
  }

  @Get('/health')
  @Public()
  health(ctx: RequestContext) {
    return ctx.json({ status: 'ok' })
  }

  @Delete('/:id')
  @Roles('admin')
  remove(ctx: RequestContext) { ... }
}

Custom strategies use createAuthStrategy() — same call/.scoped() ergonomics as defineAdapter.

Documentation

forinda.github.io/kick-js/guide/authentication — every strategy, OAuth + PKCE, CSRF, RBAC, policies, test mode.

License

MIT