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

@contextrie/cli

v0.1.2

Published

Command-line interface for Contextrie.

Downloads

25

Readme

contextrie-cli

Node CLI for indexing local sources and composing task-specific context with Contextrie.

The CLI writes its working files under .contextrie/ in the current project:

  • config.json: saved model/provider configuration
  • sources.json: indexed source manifest
  • context.md: composed context for the current task

Quickstart

Install globally with npm:

npm install -g contextrie-cli

Then run:

contextrie --index --all --openai-api-key "$OPENAI_API_KEY" --openai-base-url "$OPENAI_BASE_URL" --openai-model "gpt-5.4"
contextrie --task "Summarize the files most relevant to parser source path handling."

For local development with Bun:

bun install
bun run ./index.ts --index --all --openai-api-key "$OPENAI_API_KEY" --openai-model "gpt-5.4"
bun run ./index.ts --task "Summarize the files most relevant to parser source path handling."

Use --openai-base-url as well if you are targeting an OpenAI-compatible provider.

For the standalone macOS arm64 binary, use the separate compiled artifact and Homebrew flow. That is distinct from the npm bin entrypoint.

Usage

bun run ./index.ts --help
Usage
  $ contextrie --index [paths...]
  $ contextrie --task "describe the task"

Index sources

Index explicit files, directories, or globs:

bun run ./index.ts --index README.md core parsers

Index all supported source files in the current repository:

bun run ./index.ts --index --all

Supported files are filtered through @contextrie/parsers, and indexed metadata is written to .contextrie/sources.json.

Compose task context

After indexing, compose a task-specific context bundle:

bun run ./index.ts --task "Explain which files matter most for the CLI indexing flow."

This writes the final output to .contextrie/context.md.

Configuration

The CLI resolves configuration from:

  1. command flags
  2. .contextrie/config.json
  3. environment variables

Required:

  • OPENAI_API_KEY
  • OPENAI_MODEL

Optional:

  • OPENAI_BASE_URL

Status

Early development; expect breaking changes.