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

@illodev/workfile

v0.9.1

Published

Repository-native protocol and local MCP server for Work, Docs, History and durable project Memory.

Readme

@illodev/workfile

Repository-native protocol and local MCP server for Work, Docs, History and durable project Memory — everything lives as Markdown with restricted frontmatter inside your repository, owned by git, readable without any tool.

This package ships the complete surface: the workfile CLI, the programmatic core, a local HTTP API, a precompiled web interface and an MCP server for agents. It depends on nothing but @types/node; installing it adds no runtime tree to your project.

npm install -D @illodev/workfile     # or pnpm add -D / yarn add -D / bun add -d
npx workfile init
npx workfile ui                      # local interface
npx workfile mcp                     # MCP server (stdio)

What you get

  • Work — cards (T-NNNN) with statuses, areas, claims with actor and scope, hierarchy and archival. Sequential IDs heal deterministically after parallel-clone collisions (workfile card renumber --duplicates).
  • Docs — indexed read-only documents from your existing Markdown plus managed documents with stable IDs and review intervals.
  • History — changelog fragments merged into releases; the rendered changelog is derived, never hand-edited.
  • Memory — learnings, decisions, incidents, conventions and context as typed collections agents can query before repeating a mistake.
  • Agents — one canonical protocol synchronized into AGENTS.md, CLAUDE.md, Cursor and Copilot as compact managed blocks; workfile agents context --card T-0001 returns a bounded context bundle.
  • Doctorworkfile doctor validates the whole workspace and exits non-zero on errors, which makes it a natural CI and pre-commit gate.
  • Search — one query grammar across CLI, HTTP, MCP and UI; hybrid semantic ranking activates only when the repository explicitly declares a provider such as @illodev/workfile-search-local.

Workfile never sends repository content to a network service by itself.

As an MCP server

Point a client at it without installing anything. This is the invocation the official registry publishes for io.github.illodev/workfile:

{
  "mcpServers": {
    "workfile": {
      "command": "npx",
      "args": ["-y", "@illodev/workfile", "mcp"]
    }
  }
}

mcp is a subcommand, not a binary. Append --root PATH when the client starts somewhere other than the workspace, and --read-only to serve the read tools alone.

What it is not

Workfile is not an agent configurator. It does not install agents, ship a persona, route models or curate skills — tools like gentle-ai do that, and the two compose, because a well-configured agent still needs somewhere durable to write down what it did. Workfile answers what was done, who holds it and on what evidence, in files that outlive the agent, the session and this package. The boundaries section of the repository README makes the distinction concrete.

Documentation

Shipped inside this package under docs/:

  • Getting started — install, initialize, first loop.
  • CLI reference — every command, the query grammar, exit codes.
  • MCP server — tools, resources, prompts, the Claude Code plugin.
  • HTTP API — endpoints, conventions, stable error codes.
  • Interface — the local UI and the static demo build.
  • Security — threat model of the local server.
  • Specification — the normative protocol contract.

Repository

Part of the illodev/workfile monorepo — a pnpm workspace whose private root carries the version every published package ships with, in lockstep. The project develops itself with its own protocol: the cards, changelog and memory of this package's development live in the repository's .project/ directory.

License

MIT