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

thomas-middleware

v1.0.1

Published

Middleware Express para el protocolo thomas/encrypted E2E — descifra peticiones y cifra respuestas

Readme

thomas-middleware

Middleware Express para el protocolo thomas/encrypted E2E.

Abstrae la complejidad del cifrado/descifrado en un único middleware reutilizable.
Sin dependencias de process.env ni tipos propietarios de ningún proyecto.
Depende de thomas-encryptation para toda la lógica criptográfica.

Instalación (local)

"thomas-middleware":    "file:../thomas-middleware",
"thomas-encryptation": "file:../thomas-encryptation"

Uso

import express from 'express';
import { createThomasMiddleware } from 'thomas-middleware';

const app = express();

// La clave privada viene de tu sistema de configuración, NO de process.env hardcodeado
app.use(createThomasMiddleware({
  privateKey:      myConfig.thomasPrivateKey,         // PKCS8 PEM — requerida
  maxPayloadBytes: 10 * 1024 * 1024,                  // 10 MB (opcional, default: 5 MB)
  onError: (ctx, err) => logger.error({ ctx, err }),  // opcional
}));

// DESPUÉS del middleware thomas
app.use(express.json());

app.post('/api/users', (req, res) => {
  // req.body ya está descifrado
  // res.json() cifrará automáticamente si el cliente envió Accept: thomas/encrypted
  res.json({ ok: true, data: req.body });
});

Comportamiento

| Header de entrada | Acción | |---|---| | Content-Type: thomas/encrypted | Lee chunks → descifra body → asigna req.body | | Accept: thomas/encrypted | Parchea res.json() para cifrar la respuesta con K_resp | | X-Thomas-Response-Key (GET) | Descifra K_resp del header → parchea res.json() | | Ninguno | next() sin modificar nada |

Errores HTTP estándar

| Código | Causa | |---|---| | 413 | Payload supera maxPayloadBytes | | 400 | Body no es JSON válido o payload malformado | | 400 | No se pudo descifrar (clave incorrecta, datos corruptos) | | 500 | Error al cifrar la respuesta |

Configuración (IThomasMiddlewareConfig)

interface IThomasMiddlewareConfig {
  privateKey:       string;   // PKCS8 PEM — requerida
  maxPayloadBytes?: number;   // default: 5 MB
  onError?:         (context: string, error: unknown) => void; // default: console.error
}

Dependencias

  • thomas-encryptation — core criptográfico (local)
  • express — peer dependency (≥ 4.0.0)