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

@tarileo/artifact-omp

v0.5.0

Published

Pi/omp extension for `artifact-cli`: lets coding agents create, read, update, and list HTML artifacts without hand-writing `docs/artifacts/`.

Readme

@tarileo/artifact-omp

Pi/omp extension for artifact-cli: lets coding agents create, read, update, and list HTML artifacts without hand-writing docs/artifacts/.

Toolchain: Bun only. No npm/pnpm/yarn.

Install

From npm (any pi session for that user):

omp plugin install @tarileo/artifact-omp

From source:

git clone https://github.com/leobar37/artifacts-cli.git
cd artifacts-cli
bun install
bun run --cwd packages/store build
bun run --cwd packages/pi-extension build
omp plugin link ./packages/pi-extension

Uninstall (verifies rollback path):

omp plugin remove @tarileo/artifact-omp
# if that flag doesn't exist in your omp version: omp plugin --help

What the agent gets

| Tool | Purpose | |---|---| | artifact_create | Save standalone HTML as a versioned artifact. Returns OK <slug>@<version> + file path + repoId + shareable view: link. | | artifact_read | Read HTML for editing only (latest or version, offset/limit paging). Never use it to show content to the user. | | artifact_update | Save a new version (never rewrites). Pass baseVersion from artifact_read; on mismatch returns CONFLICT instead of overwriting. Returns the view: link. | | artifact_versions | Version history JSON for rollback picks. | | artifact_list | All artifacts in the current repo. | | artifact_show | Shareable dashboard link for an artifact (artifact: URL with ?select=<slug>), or the all-artifacts overview with no slug. Use it whenever the user asks to see, show, open, or explain an artifact. |

Plus:

  • /artifact show [slug] slash command (dashboard link) and /artifact list (slugs + overview link).
  • artifacts://<slug> / artifacts://<slug>/<version> read-only protocol for omp's read tool (immutable; best-effort — tools work even if the omp internal router moved).

Model (does not change)

  • Content tools write through @tarileo/artifact-store (LocalStore) directly: no daemon needed for create/read/update. Only link resolution (artifact_show, view: lines, /artifact show) reads ~/.artifact/daemon.json and probes /api/health — best-effort, never fails a write.
  • Source of truth: global store ~/.artifact/store/<repoId>/ (stable id across worktrees). Each save creates versions/vNNN, updates index.html + meta.json + manifest.json, and leaves docs/artifacts/<slug>/index.html as a symlink.
  • The dashboard sees tool writes via symlink + watcher.
  • Slugs are normalized (slugify: lowercase, strip accents, non-alphanumeric → -, max 60 chars).

Error contract (stable, agents rely on it)

  • OK <slug>@<version> — write succeeded.
  • NOT_FOUND <slug>[@<version>] — read/update/versions on unknown slug. Updates must tell the agent to use artifact_create.
  • CONFLICT <slug>: latest is <v>, base was <v> — artifact_update with stale baseVersion. Agent must artifact_read again and retry.
  • NO_DAEMON ... Start with: artifact start — artifact_show (or empty view:) when the daemon lock is missing or the daemon doesn't answer /api/health. Same message as CLI artifact url.

Dev

bun run --cwd packages/pi-extension build      # tsc → dist/
bun run --cwd packages/pi-extension typecheck  # tsc --noEmit
bunx vitest run packages/pi-extension          # protocol tests

Publish only via GitHub Release (omp-v* tag triggers publish.yml); never npm publish by hand.