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

@easylegal/node

v0.1.0

Published

EasyLegal server SDK — session token minting and webhook signature verification. The only place your secret key belongs.

Readme

@easylegal/node

Server SDK for EasyLegal — embeddable contract infrastructure. This package is the only place your EasyLegal secret key belongs: it mints the short-lived session tokens your frontend uses, and verifies signatures on webhooks and data-connector requests.

npm install @easylegal/node

Mint session tokens (required)

Your server exchanges its secret key for a 15-minute, workspace-scoped JWT. Hand only the token to the browser; re-mint freely on expiry.

import { EasyLegal, EasyLegalError } from "@easylegal/node";

const easylegal = new EasyLegal({ secretKey: process.env.EASYLEGAL_SECRET_KEY });

// e.g. a Next.js route handler at /api/easylegal/session
export async function POST() {
  try {
    const session = await easylegal.sessions.create({
      // Your own stable id + display name for this business/workspace.
      workspace: { externalRef: firm.id, name: firm.name },
      user: { id: currentUser.id, role: "owner" }, // optional attribution
    });
    return Response.json(session); // { token, expiresAt }
  } catch (err) {
    if (err instanceof EasyLegalError) {
      // 402 + reason "account_lapsed" → render your locked/paywall state.
      return Response.json({ error: err.message, reason: err.reason }, { status: err.status });
    }
    throw err;
  }
}

Workspaces are upserted by externalRef — no separate provisioning call.

Verify webhooks

EasyLegal signs outbound webhooks HMAC-SHA256 over ${timestamp}.${body} (easylegal-signature: t=<unix>,v1=<hex>), with a freshness tolerance so captured requests can't be replayed.

const ok = easylegal.webhooks.verify(rawBody, req.headers["easylegal-signature"], signingSecret);

Data connector (bulk & background sends)

When a send references one of your records by id instead of inlining the payload, EasyLegal fetches it from the connector URL you registered in the dashboard. Verify the signature over the raw body, scope the lookup, and return the same payload shape you registered:

export async function POST(req: Request) {
  const raw = await req.text();
  if (!easylegal.connector.verify(raw, req.headers.get("x-easylegal-signature") ?? "", signingSecret))
    return Response.json({ error: "bad signature" }, { status: 401 });

  const { subjectRef, workspaceExternalRef } = JSON.parse(raw);
  const record = await findRecord(workspaceExternalRef, subjectRef);
  if (!record) return Response.json({ error: "unknown subject" }, { status: 404 });
  return Response.json(record.payload);
}

Your signing secret lives in the EasyLegal dashboard (Payload schema → Data connector). Zero dependencies; Node 18+.