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

@abzedsync/engine

v1.3.0

Published

AbzedSync local agent - progress publishing, shared doc sync, and GitLab send CLI (`abzedsync`)

Readme

@abzedsync/engine

AbzedSync local agent - a cross-platform project sync engine that watches local code changes, publishes manager-friendly work items to the AbzedSync control plane, keeps shared docs in sync, and sends eligible items to GitLab when asked.

Install

npm install -g @abzedsync/engine

Requires Node.js 18 or newer. Supported platforms: Linux, macOS, Windows.

Quick start

# 1. Authenticate against the AbzedSync control plane
abzedsync login

# 2. Initialize a project in the current directory
cd /path/to/your/repo
abzedsync init

# 3. Start the watcher
abzedsync start

# 4. Publish current work for visibility only
abzedsync progress --push

# 5. Send eligible work to GitLab when you want it published there
abzedsync gitlab --push

Commands

| Command | Purpose | | --- | --- | | abzedsync login | Sign in to the AbzedSync control plane | | abzedsync init | Register the current repo as a project side | | abzedsync start | Start the long-running watcher | | abzedsync stop | Stop the watcher for this project | | abzedsync status | Show current agent status | | abzedsync sync --push | Push local docs/project-apis.md into the shared store | | abzedsync sync --pull | Pull the latest shared docs/project-apis.md into this repo | | abzedsync sync --merge | Merge frontend/backend shared doc snapshots into a fresh canonical copy | | abzedsync progress --push | Publish engine-detected changes to AbzedSync (publish/view-only) | | abzedsync progress --stats | Show progress counts for the project | | abzedsync gitlab --push | Send every eligible unsent active-queue item directly to GitLab | | abzedsync gitlab --push --ids <uuids> | Send only the listed items | | abzedsync accept | Resolve a sync conflict by accepting a side | | abzedsync logs | Tail the engine log output |

Runtime state

The agent stores session and project state under the user's home directory:

~/.abzedsync/
  config.json
  session.json
  pids/
  logs/
  shared-docs/

Per-project state lives in the repo where you ran abzedsync init:

<project>/
  .abzedsync.json
  docs/
    project-apis.md
  project-sync/

Sync behavior

  • abzedsync progress --push is publish/view-only. It makes detected work visible in AbzedSync and does not talk to GitLab.
  • abzedsync gitlab --push sends eligible unsent items directly to GitLab and archives them out of the active queue on success.
  • abzedsync sync --merge reads the latest frontend/backend shared doc snapshots, merges matching top-level sections, and preserves both sides when their content still differs.

GitLab connection

GitLab linking happens in the AbzedSync app under Settings -> Profile. The CLI checks the live backend account state before GitLab send commands.

License

UNLICENSED - internal distribution.