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

lazyaif

v0.8.0

Published

Analyze ai-factory plan statuses (fast/full) via TUI or CLI

Readme

lazyaif

Platform of tools for analyzing ai-factory project artifacts.

Commands

lazyaif              → TUI dashboard (default = plans-viewer)
lazyaif tui          → TUI (explicit)
lazyaif plans        → CLI: plans table
lazyaif plans --json → JSON
lazyaif p            → alias for plans
lazyaif status        → CLI: brief summary
lazyaif --help        → commander auto-help
lazyaif --version     → 0.1.0

Install

cd packages/aif-plans
npm install

Usage

CLI

npm run plans                          # scan .ai-factory/ in cwd
npm run plans -- --path ../other-proj  # scan a different project
npm run plans -- --json                # output JSON
npm run status                         # brief summary

TUI

npm run tui                            # interactive viewer on cwd
npm run tui -- --path ../other-proj    # scan a different project

Layout

By default the TUI shows two panes side by side:

  • Left (40%) — list of plans (kind, filename, progress, counts, age)
  • Right (60%) — flat list of Tasks of the currently selected plan (/ checkbox, id: title), updates as you navigate with arrows

On small terminals (width < 100 columns) the Tasks pane is hidden automatically and the plan list takes the full width. Enter/Tab switches to the detail view (full-width markdown of the selected plan), Esc/Tab returns to the list view and restores the Tasks pane.

TUI Runtime Requirements

The TUI uses OpenTUI which requires FFI:

  • bun — FFI out of the box, recommended
  • Node >=26.3 — run with node --experimental-ffi

CLI mode works on any Node >=20 without FFI.

Architecture

bin/lazyaif.ts           → commander router (tui | plans | status)
src/app/                 → orchestration (tui-dashboard, cli-dispatch)
src/views/               → UI per module (plans-viewer, status)
  plans-viewer/           → tui-view, cli-view, web-view (stub)
  status/                 → tui-view, cli-view
src/clients/             → generic display frameworks
  tui/                    → createTuiRenderer + components (header, footer, theme)
  cli/                    → table helpers, json renderer
  web/                    → (stub, отложен)
src/modules/             → domain logic (no UI deps)
  plans-viewer/           → types, parser, scanner, status, format
  status/                 → types, summary (depends on plans-viewer)
src/shared/              → common utilities (placeholder)
tests/modules/           → tests per module
tests/fixtures/          → test data

Dependency rule

modules/     → no client deps (pure logic)
clients/     → no module deps (generic frameworks)
views/       → depends on modules + clients (binding layer)
app/         → depends on views (orchestration)
shared/      → depends on nothing (base layer)

Tests

npm test