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

@ltikit/adapter-prisma

v0.1.1-rc.4

Published

Prisma PlatformStore + NonceStore adapters for ltikit — any Prisma-supported database.

Readme

@ltikit/adapter-prisma

Prisma PlatformStore + NonceStore for LTIkit — works against any Prisma-supported database (SQLite, Postgres, MySQL, ...). Bring your own Prisma schema; this adds two small models and maps them to the core stores.

Requires @ltikit/core.

npm i @ltikit/core @ltikit/adapter-prisma

1. Add the models

Copy the two models from prisma/schema.example.prisma into your own schema.prisma, then migrate:

npx prisma migrate dev --name add_ltikit

2. Wire the stores

import { PrismaClient } from '@prisma/client'
import { createLti, staticKeyStore } from '@ltikit/core'
import { prismaPlatformStore, prismaNonceStore } from '@ltikit/adapter-prisma'

const prisma = new PrismaClient()

export const lti = createLti({
  keys: staticKeyStore({ /* ...your tool keypair... */ }),
  platforms: prismaPlatformStore(prisma),
  nonces: prismaNonceStore(prisma),
})

No hard dependency on @prisma/client: the client is accepted structurally (PrismaLike — just the ltiPlatform / ltiNonce delegates), so any generated PrismaClient whose schema matches the two models above satisfies it automatically.

Notes

  • Single-use nonces are enforced by Prisma's per-row atomic delete — a replayed state hits a missing row (Prisma's P2025), which consume turns into null.
  • Also implements the writable MutablePlatformStore contract, so Dynamic Registration auto-persists new platforms with no manual insert.
  • Different model names? Pass an object matching PrismaLike that aliases your own delegates: prismaPlatformStore({ ltiPlatform: prisma.myModel, ltiNonce: prisma.myOtherModel }).

Docs

Links

Repository · Issues · Need help? — paid setup/integration help available.

MIT