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

poly-weaver

v1.3.3

Published

Orchestrates pluggable AI coding agents in an iterative plan-review loop

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

shihaoheshihaohe

Keywords

Readme

poly-weaver

A minimal agent workflow for shipping day-to-day features.

Watch the poly-weaver demo video

poly-weaver startup TUI

Installation

Prerequisites

  • Node.js 22.17 or newer, with the 23.x line excluded (22.17+, 24.x, 25.x, and 26.x+ are supported; only 23.x is not). On Windows, this Node floor is required for libuv raw VT input so ConPTY can deliver mouse wheel, Shift+Tab, kitty keyboard protocol, and bracketed-paste delimiters as VT bytes. Older Node versions still handle ordinary typing and basic control/navigation keys, but those richer terminal inputs degrade.
  • A C++ toolchain for node-pty:
  • At least one supported agent CLI installed and authenticated:
npm install -g poly-weaver

Usage

poly-weaver

This opens an interactive TUI to configure the task, select providers for each role, and set options before starting the orchestration loop.

You can seed TUI defaults from a JSON config file:

poly-weaver --config <path-to-config.json>

Note: poly-weaver's auto-update of the agent CLIs (Claude Code, Codex CLI, GitHub Copilot CLI) currently supports only npm and winget as installation sources — an agent CLI is auto-updatable only if it was installed via npm or winget. Other installation sources are not supported. This applies to agent-CLI auto-update only, not poly-weaver's own self-update. Npm update checks and installs use your configured registry and settings, including min-release-age. Claude Code and Codex CLI updates select only clean stable versions; GitHub Copilot CLI and poly-weaver follow their normal latest tag.

CLI options

| Option | Description | Default | |---|---|---| | --config <path> | Path to a JSON config file | (none) | | -h, --help | Show help | | | -V, --version | Show version | |

Workflow is selected with Shift+Tab in the TUI. Built-in workflows are default, simplify, and crosscheck. Custom flows remain available as deprecated compatibility behavior.

Managed poly-spec mode

The built-in default workflow has an optional Manage Spec with poly-weaver toggle. On a fresh run it defaults on when the working directory contains .poly-spec/, and defaults off otherwise. When enabled, the interviewer owns a repository-managed Iteration Spec under .poly-spec/iterations/pending/ plus a session-local Iteration Rationale. The Iteration Spec is the authoritative requirements source for planning, review, and implementation; the Iteration Rationale is supporting context.

Plan Only sessions stop after the accepted plan and are terminal. In managed mode they leave the Iteration Spec pending; later work may continue it, but must start a new workflow and approve a new plan.

Managed sessions resume only interrupted active work. Resume re-reads the current worktree Iteration Spec path recorded in the session manifest, so repository edits to .poly-spec/iterations/pending/*.md remain authoritative. At terminal completion of a non-Plan-Only managed run, the Iteration Spec moves to .poly-spec/iterations/applied/ as immutable history; applied placement does not imply implementation-review approval.

License

MIT