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

@forjio/sdk

v0.9.0

Published

Shared SDK for the Forjio commerce suite. JWT middleware, ARN parser, event envelope, outbox helpers, HTTP envelope types, OIDC device-flow auth, multi-profile session store, typed API client.

Readme

@forjio/sdk

Shared TypeScript SDK for the Forjio commerce suite.

Consumed by every product repo: huudis, plugipay, storlaunch, fulkruma, ripllo, malapos, suppuo.

What's in here

| Module | Purpose | |---|---| | @forjio/sdk/auth | JWT verification middleware (JWKS cache + ES256), OIDC client helpers. | | @forjio/sdk/arn | ARN parser + builder. forjio:<service>:<region>:<accountId>:<type>/<id> (see ADR-0008). | | @forjio/sdk/events | Event envelope type + ULID event ID generation + outbox helpers (write event inside transaction, read unpublished batch, mark published). | | @forjio/sdk/http | Response envelope type { data, error, meta }, shared validators. | | @forjio/sdk/iam | Policy evaluator, canned policy loader, condition key set. Implements the AWS-IAM-JSON policy language defined in ADR-0003. |

Install

npm install @forjio/sdk

Example: verify a Huudis JWT in an Express route

import { verifyAccessToken } from '@forjio/sdk/auth';

app.use(async (req, res, next) => {
  const token = req.headers.authorization?.replace(/^Bearer /, '');
  if (!token) return res.status(401).json({ error: { code: 'AUTH_REQUIRED' } });
  try {
    req.auth = await verifyAccessToken(token, {
      issuer: 'https://huudis.com',
      audience: 'plugipay',
    });
  } catch (err) {
    return res.status(401).json({ error: { code: 'INVALID_TOKEN' } });
  }
  next();
});

Example: emit an outbox event inside a Prisma transaction

import { writeOutboxEvent } from '@forjio/sdk/events';

await prisma.$transaction(async (tx) => {
  const session = await tx.checkoutSession.update({
    where: { id },
    data: { status: 'completed' },
  });
  await writeOutboxEvent(tx, {
    type: 'plugipay.checkout.completed.v1',
    accountId: session.accountId,
    data: { sessionId: session.id, amount: session.amount, currency: session.currency },
  });
});

Versioning

Semver. Breaking changes bump major. Products upgrade on their own cadence. Published on every merge to master.

Non-goals

  • Not a business-logic library. Service-specific logic lives in each product repo.
  • Not a Prisma schema share. Each service owns its own schema (see ADR-0001).
  • Not an auto-generated REST client. We use handwritten thin clients with shared types — better DX than OpenAPI codegen at our scale.