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

@flue/cli

v0.0.49

Published

CLI for running [Flue](https://github.com/withastro/flue) AI-enabled workflows, locally or in GitHub Actions.

Readme

@flue/cli

CLI for running Flue AI-enabled workflows, locally or in GitHub Actions.

Install

bun install @flue/cli
npm install @flue/cli
pnpm install @flue/cli

Usage

flue run <workflowPath> [--args <json>] [--model <provider/model>] [--sandbox <image>]
flue run .flue/workflows/triage.ts
flue run .flue/workflows/triage.ts --model anthropic/claude-sonnet-4-5
flue run .flue/workflows/triage.ts --args '{"issueNumber": 123}'
flue run .flue/workflows/triage.ts --sandbox my-org/my-sandbox:latest

The CLI auto-starts an OpenCode server if one isn't already running. The opencode binary must be installed and on PATH.

Sandbox Mode

The --sandbox <image> flag runs the OpenCode server inside a Docker container for security isolation. The LLM and its tool calls execute inside the container, while the host retains control of secrets (like API keys). Shell commands via flue.shell() also execute inside the container.

Prerequisites: Docker (GitHub Actions supported). Your container image must have OpenCode and git installed, and should start the OpenCode server on port 48765. Any other tools your workflows need (e.g., curl, pnpm) can be added to the image as well.

Model Configuration

The CLI uses the local OpenCode server's model configuration. Either:

  • Pass --model to the CLI: flue run workflow.ts --model anthropic/claude-sonnet-4-5
  • Or set "model" in your project's opencode.json

Provider API keys (e.g. ANTHROPIC_API_KEY, OPENAI_API_KEY) are read from the environment at runtime.