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

wiki-graph-job

v0.8.3

Published

Runtime-neutral chapter build engine for Wiki Graph.

Downloads

566

Readme

wiki-graph-job

Runtime-neutral chapter build engine shared by wiki-graph-core and the hosted wg-job service.

The package owns the six chapter JSONL input and artifact contracts, their validation, and the build algorithms. A host gives it an input file, a revision, and an empty request-scoped directory; the result is an artifact JSONL file plus the same revision. Hosts inject LLM, embedding, WikiSpine and Wikimedia capabilities. Queue state, .wikg access, HTTP transport, artifact application, and provider selection remain host responsibilities.

Reading-summary completion is independent of text length. Every successful reading-summary artifact contains at least one summary-part record. An empty result is represented explicitly by {"type":"summary-part","position":0,"text":""}; a zero-byte artifact is invalid. Positions start at zero and are contiguous and unique.

Applying an explicit empty summary creates a present, empty summary text stream. Chapter stage, SDK inspection, and CLI state therefore report it as completed even though it has no sentences. Missing and empty summaries are distinct; resetting the reading graph or changing source removes completion.

An empty summary-embedding snapshot is valid for a completed empty summary. Like an empty source-embedding snapshot, it produces an embedding-metadata record with no segments and does not call the embedding provider. Applying it creates a current empty index, distinct from a missing index.