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

@vivantel/virage-dashboard

v0.1.25

Published

React dashboard web app for the Virage RAG pipeline — served by virage-cli

Readme

@vivantel/virage-dashboard

npm version License: MIT

React monitoring dashboard for the Virage RAG pipeline, served by virage dashboard.

Usage

virage dashboard                  # start on port 3000
virage dashboard --port 8080      # custom port
virage dashboard --verbose        # log every HTTP request (useful for debugging)

The CLI prints the UI path and database status on startup. If the UI is missing it serves an actionable build-instructions page instead of a blank screen.

Pages

| Page | Description | | ----------- | ---------------------------------------------------------------------------------- | | Home | Live chunk count, embedding count, memory usage, chunk-size histogram (from vector DB), anomaly table | | Chunks | Browse and delete individual chunks by source file | | Search | Semantic search with extended chunk info: denseText, sparseText, metadata key-value pairs, generator IDs; virtual scroll; sort by similarity or chunk size | | Pipeline | Trigger pipeline operations via WebSocket (index, eval-generate, eval-run); shared PipelineLog component shows live progress | | Experiments | View, compare, and delete saved evaluation runs; PipelineLog appears only for eval-save / eval-run ops — pipeline index logs are filtered out | | Analytics | Query history, top search terms, zero-result queries, queries-per-hour chart |

Data sources

| Data | Source | |------|--------| | Chunk text, vectors, metadata | LanceDB (vectorStore.listAll() / vectorStore.search()) | | Chunk-size histogram | Computed from LanceDB data; empty-state card shown before first virage index | | System stats, analytics, experiment runs | SQLite (VirageDb) |

All endpoints fall back to SQLite when a vector store config is unavailable.

Search page

Results include all fields stored in LanceDB:

  • denseText — the embedding-target text (displayed by default)
  • sparseText — BM25 tokens (visible on expand)
  • metadata — key-value pairs from the chunker (expand to see)
  • sparseTextGeneratorId / metadataGeneratorId — chunker fingerprints (expand to see)
  • sourceFile and similarity % — always visible in collapsed card

Results can be sorted by Vector Similarity (default) or Chunk Size.

Pipeline log

The shared PipelineLog component (src/components/PipelineLog.tsx) renders WebSocket progress messages and is used by both Pipeline and Experiments pages. It filters by currentOp — the Experiments log only shows eval-save and eval-run ops; pipeline ops (index, eval-generate) do not appear there.

Development

# In one terminal — start the virage-cli API server
cd packages/virage-cli && npx tsx src/bin/virage.ts dashboard

# In another terminal — start the Vite dev server (proxies /api and /ws → localhost:3000)
cd packages/virage-dashboard && npm run dev

Rebuild the production bundle and embed it in virage-cli:

npm run build:with-dashboard -w @vivantel/virage-cli

Testing

npm test                          # unit tests (vitest)
npm run test:e2e                  # E2E tests (playwright; starts dev server automatically)
npm run type-check                # TypeScript

See docs/ai/guardrails/dashboard.md for architecture, component conventions, and testing patterns.

License

MIT