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

@pompelmi/nextjs

v1.0.0

Published

Next.js middleware for pompelmi — in-process ClamAV virus scanning with zero extra dependencies

Readme

@pompelmi/nextjs

Next.js middleware for pompelmi — in-process ClamAV virus scanning with zero extra dependencies.

Supports both the App Router (Next.js 13+) and the Pages Router (Next.js ≤ 12).

Installation

npm install pompelmi @pompelmi/nextjs

ClamAV must be available on the server — either via the system clamscan binary or a running clamd daemon.

App Router (Next.js 13+)

// app/api/upload/route.js
import { withPompelmi } from '@pompelmi/nextjs'

export const POST = withPompelmi(async (req) => {
  const formData = await req.formData()
  const file = formData.get('file')
  // req.pompelmiVerdict is set — Verdict.Clean is guaranteed here
  return Response.json({ ok: true })
}, {
  host: 'localhost',
  port: 3310,
})

With TypeScript:

// app/api/upload/route.ts
import { withPompelmi } from '@pompelmi/nextjs'

export const POST = withPompelmi(async (req: Request) => {
  return Response.json({ ok: true })
}, { host: 'localhost', port: 3310 })

Pages Router (Next.js ≤ 12)

// pages/api/upload.js
import { withPompelmiHandler } from '@pompelmi/nextjs'

async function handler(req, res) {
  // req.pompelmiVerdict is set — Verdict.Clean is guaranteed here
  res.json({ ok: true })
}

export default withPompelmiHandler(handler, {
  host: 'localhost',
  port: 3310,
})

Options

All options are forwarded to pompelmi.scanBuffer():

| Option | Type | Default | Description | |---|---|---|---| | host | string | — | clamd hostname (TCP mode) | | port | number | 3310 | clamd port | | socket | string | — | UNIX socket path | | timeout | number | 15000 | Connection timeout in ms | | retries | number | 0 | Auto-retry count on failure |

When neither host nor socket is provided, pompelmi falls back to the local clamscan binary.

Behaviour

  • The raw request body is buffered and scanned before your handler runs.
  • If the body is malicious, a 400 JSON response is returned immediately: { "error": "Malicious file detected" }.
  • req.pompelmiVerdict is set to the Verdict symbol so your handler can inspect it if needed.
  • Scan errors (e.g. clamd unreachable) are not blocking — the request proceeds with Verdict.ScanError.

License

ISC