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

@hanzo/cd

v0.1.1

Published

Hanzo GitOps — a presentational, data-prop-driven React surface for a full CD/GitOps console: an applications list, an app detail shell, a health/sync color-coded resource-tree topology (reusing @hanzo/canvas's deterministic layout), resource node info (l

Readme

@hanzo/cd

A presentational, data-prop-driven React surface for a full CD/GitOps console — a clean-room port of the Argo CD UI (Apache-2.0; see NOTICE). Every component takes typed props and renders; it never fetches. The embedding app wires the Hanzo native CD API (/v1/gitops) and maps its rows into these view-models.

import {
  GitopsAppList,      // applications grid/table (health, sync, revision, search)
  GitopsAppDetails,   // the app view shell (header + tree + node panel + sync)
  GitopsAppTree,      // resource-tree topology (health/sync color-coded, pan/zoom)
  GitopsNodeInfo,     // node drill-in: manifest / diff / events / logs
  GitopsSyncPanel,    // sync + rollback panel
  GitopsRollbackDialog,
  GitopsDiffView,     // colorized desired-vs-live unified diff
  ResourceNode,       // a single resource card (kind + health + sync)
  HealthBadge,        // Healthy / Progressing / Degraded / Suspended / Missing / Unknown
  SyncBadge,          // Synced / OutOfSync / Unknown
  GitopsStyles,       // one <style> tag: theme-aware CSS for the whole surface
} from '@hanzo/cd'

Design

Two orthogonal status axes, exactly as Argo CD models them — never conflated:

  • HealthHealthy | Progressing | Degraded | Suspended | Missing | Unknown
  • SyncSynced | OutOfSync | Unknown

The pure folds (foldHealth, foldSync, buildResourceGraph, classifyDiff) are React-free and unit-tested in isolation, importable without pulling in any component:

import { foldHealth, foldSync, buildResourceGraph, classifyDiff } from '@hanzo/cd/pure'

The resource-tree topology reuses @hanzo/canvas's deterministic layered layout (layoutGraph) — no separate graph dependency. Nodes are laid out left-to-right by parent references (Application → Service → Deployment → ReplicaSet → Pod, plus Ingress, ConfigMap, certificates…) and color-coded by health and sync.

Theming

Presentational and theme-aware. Mount <GitopsStyles /> once (or inline GITOPS_CSS); drive the theme prop off your app's resolved theme. Status colors are semantic (Argo CD hues) and overridable via the healthPalette / syncPalette props. Migrates cleanly to @hanzo/gui primitives when that base lands — the components are clean-room React over a small scoped stylesheet.