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

@plurnk/plurnk-service

v1.0.5

Published

Plurnk agent runtime — the server / engine / core. Implements the @plurnk/plurnk-grammar contract.

Readme

plurnk-service

LLM agent runtime engine. Consumes plurnk-grammar; exposes WebSocket JSON-RPC. User-facing CLI: plurnk. Provider-agnostic, MIT — no vendor or model lock-in.

What an agent can do

Grammar ops: PLAN reason · READ/EDIT files · FIND search · EXEC run shell/code · SEND message or conclude · COPY/MOVE/KILL manage · OPEN/FOLD curate its own context.

Over schemes: file:// project files · exec:// command output · http(s):// web fetch · run:// sibling agent runs (spawn / fork / message) · known:// scratch · log:// own history.

Loop model

Session = the shared world (one filesystem + membership overlay). Run = one agent's private log. Loop = one prompt → ops → SEND[terminal] cycle; every turn leads with PLAN. Runs fork and message each other — many clients, many runs, one session.

Integration (WebSocket JSON-RPC)

Methods: session.* (create / attach / constrain / list…) · loop.run / loop.inject / loop.resolve · op.* (read / edit / find / exec / send…) · log.read · run.fork. Streams: log/entry → … → loop/terminated, plus loop/proposal, telemetry/event. Full live catalog: the discover RPC.

ws connect → session.create({ projectRoot }) → loop.run({ prompt })
           → read log/entry notifications until loop/terminated

The human CLI over this surface is plurnk.

Run

npm install -g @plurnk/plurnk-service
plurnk-service start      # daemon (`migrate` initializes the DB)

Config + state live in ~/.plurnk/ (created on first run): put your config in ~/.plurnk/.env (yours, seeded once); the DB defaults to ~/.plurnk/plurnk.db. Provider-agnostic — point PLURNK_MODEL at any vendor. INSTALL.md is the config guide — the cascade, the prefix taxonomy, the coupling matrix, and profiles for common deployments; .env.defaults is the terse machine floor it breaks down (per-package, assembled at boot). Also exports { Engine, Daemon, SchemeRegistry } for in-process embedding.

Contract & siblings

Semantic search

FIND's ~query ranks semantically via an optional embedder peer, @plurnk/plurnk-mimetypes-embeddings (heavy native deps; not installed by default). Absent → ~query falls back to FTS keyword ranking and start prints an embedder inactive notice. Enable vector search: npm i @plurnk/plurnk-mimetypes-embeddings.

Tests

test:lint, test:unit, test:intg, test:live, test:demo; off-hot-path test:installation.