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

@agent-ix/filament-plan-sync

v0.1.0

Published

oclif-free engine core for plan/tracker bidirectional sync

Readme

@agent-ix/filament-plan-sync

Bidirectional synchronization between a canonical plan tree and an external issue tracker.

The engine keeps a plan tree and a tracker in agreement without either side owning the truth outright: a per-target base/shadow store records what was last agreed, a three-way merge reconciles divergence, and a conflict policy decides what a machine may resolve and what a person must.

Trackers sit behind a driver interface with an invertible hierarchy projection, so a plan's shape survives the round trip into a tracker that models hierarchy differently. GitHub (including Projects v2 boards) and Jira drivers ship with the engine. Authentication is always explicitly user-initiated.

Use

The engine carries no host assumptions. The same core runs in a hosted worker, embedded in-process, and behind a CLI command.

As an oclif core plugin it contributes a sync command to its host:

// host package.json
{
  "dependencies": { "@agent-ix/filament-plan-sync": ">=0.1.0" },
  "oclif": { "plugins": ["@agent-ix/filament-plan-sync"] }
}

The host's oclif Config loader discovers it as a core plugin — bundled as a dependency, with no runtime install step — so sync is available the moment the host is installed. @agent-ix/quoin ships it this way.

Used as a library, the package's main entry exports the plan-tree model, the synchronization operations, and the driver interface directly.

Requirements

Node.js 18 or newer.

License

MIT — see LICENSE.