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

@kirkelabs/open-agent-access-vercel

v0.1.0

Published

Vercel and Next.js middleware adapter for Open Agent Access policy enforcement.

Readme

@kirkelabs/open-agent-access-vercel

Vercel and Next.js middleware adapter for Open Agent Access.

Use this package when a static-first publisher, portfolio, docs site, or content site wants to publish an /.well-known/agent-access.json policy and enforce agent-specific rules at the edge.

Install

npm install @kirkelabs/open-agent-access-vercel

Next.js middleware

For Edge middleware, prefer importing the policy JSON at build time. Avoid filesystem policy reads in Edge runtime.

// middleware.ts
import policy from "./agent-access.json";
import { createAgentAccessVercelMiddleware } from "@kirkelabs/open-agent-access-vercel";

export default createAgentAccessVercelMiddleware({
  policy,
  protectedPaths: ["/essays/:path*"],
  humanFallback: "allow",
  mode: "passport-required"
});

export const config = {
  matcher: ["/essays/:path*", "/.well-known/agent-access.json"]
};

With humanFallback: "allow", normal browser requests for HTML continue to the site. Agent-like requests are evaluated against the policy and receive deterministic AA-* headers and JSON denials/review decisions when they do not meet the declared requirements.

Static policy copy

Keep agent-access.json as the source of truth and copy it to:

public/.well-known/agent-access.json

or serve it through middleware by including /.well-known/agent-access.json in the matcher.

Serverless or local mode

For non-Edge usage you may load a policy from disk:

import { createAgentAccessVercelMiddleware } from "@kirkelabs/open-agent-access-vercel";

export default createAgentAccessVercelMiddleware({
  policyPath: "./agent-access.json",
  protectedPaths: ["/essays/:path*"],
  failMode: "closed"
});

Receipts

Edge middleware should use receiptSink and write to a durable service.

createAgentAccessVercelMiddleware({
  policy,
  protectedPaths: ["/essays/:path*"],
  async receiptSink(receipt) {
    await fetch(process.env.OAA_RECEIPT_ENDPOINT!, {
      method: "POST",
      headers: { "content-type": "application/json" },
      body: JSON.stringify(receipt)
    });
  }
});

Filesystem JSONL receipts are intended for local/serverless Node contexts, not Edge runtime.