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

@dwk/ldn

v1.0.0-beta.1

Published

Linked Data Notifications (W3C LDN) primitives: inbox discovery, notification validation, and listing. RDF-only, protocol-agnostic.

Readme

@dwk/ldn

Linked Data Notifications (W3C LDN) primitives. A pure, RDF-only, protocol-agnostic library: it implements the three LDN roles as plain-data functions over @dwk/rdf's flat StoredQuad representation, with no Cloudflare bindings, no transport, and no Solid/WAC assumptions. The same primitives back the @dwk/solid-pod inbox (discovery) and the @dwk/activitypub inbox (advertisement) without either standard leaking into the other.

See the spec for the authoritative requirements.

What it does

  • Discovery — advertise an inbox with inboxLinkHeader(inboxIri) (an ldp:inbox Link value) or inboxTriple(subject, inbox) (the in-body triple), and find one from the consumer side with parseInboxLinks(header) or discoverInboxIris(quads, subject?).
  • ReceiverparseNotification(body, contentType, { baseIRI }) validates a posted RDF notification, throwing a NotificationProblem that carries the HTTP status to answer (415 for a non-RDF media type, 400 for a body that does not parse or has no triples) and otherwise returning the parsed StoredQuads.
  • ConsumerinboxListingQuads(inbox, members) builds the ldp:Container + ldp:contains listing triples; listInboxMembers(quads, inbox?) reads them back.

Authorization, deduplication, and storage are the caller's concern — this library only speaks RDF and the LDN vocabulary.

Usage

import {
  inboxLinkHeader,
  parseNotification,
  NotificationProblem,
} from "@dwk/ldn";

// Producer: advertise the inbox on a target resource's response.
response.headers.set("link", inboxLinkHeader("https://alice.example/inbox/"));

// Receiver: validate an inbound notification before persisting it.
try {
  const { quads } = await parseNotification(
    await request.text(),
    request.headers.get("content-type"),
    { baseIRI: inboxIri },
  );
  // …authorize, dedup, and store `quads`…
} catch (error) {
  if (error instanceof NotificationProblem) {
    return new Response(error.message, { status: error.status });
  }
  throw error;
}