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

@tplog/zendy

v0.2.14

Published

Internal harness for Dify Enterprise support ticket analysis, powered by pi

Vulnerabilities

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

Links

Git

Maintainers

tplogtplog

Keywords

Readme

zendy

Internal support engineering harness for Dify Enterprise. Analyze Zendesk tickets with natural language — from ticket metadata to Helm chart values to source code.

Powered by pi.

中文 | 日本語

What it does

zendy bundles three built-in skills into a single CLI:

  • zcli — Pull Zendesk ticket metadata and comment threads
  • helm-watchdog — Query Dify Helm chart values, images, and validation for any version
  • source-check — Clone and analyze Dify source code (enterprise backend/frontend, open-source core, plugin daemon, sandbox)

Typical workflow:

"Analyze ticket #1959" → pull ticket + comments → identify version →
pull Helm chart values → analyze config → (if needed) clone source →
synthesize findings → draft reply

Prerequisites

  • pi installed globally: npm install -g @mariozechner/pi-coding-agent
  • Zendesk credentials configured: zcli configure or env vars (ZENDESK_SUBDOMAIN, ZENDESK_EMAIL, ZENDESK_API_TOKEN)
  • Git SSH access to private repos (for source-check skill)

Install

npm install -g @tplog/zendy

Or clone and build from source:

git clone [email protected]:tplog/zendy.git
cd zendy
npm install
npm run build
npm link

Usage

zendy

All arguments are passed through to pi:

zendy --provider anthropic --model claude-sonnet-4-20250514
zendy -p "Analyze ticket #1959"

How it works

On first run, zendy extracts bundled skill files to ~/.zendy/<version>/ and launches pi with project-only skills (no global skills or extensions loaded).