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

djunker

v0.1.0

Published

The djunker command-line interface: encode, decode, inspect, and build D4 loot filters.

Readme

djunker

The djunker command-line interface — encode, decode, inspect, and build Diablo IV loot-filter import/export codes from a human- and AI-authorable spec.

The filter code is base64-wrapped protobuf; djunker reads and writes it directly, so you can build a filter from a readable spec instead of the in-game editor, decode any existing code back into an editable spec (full round-trip), and use capabilities the client hides (like translucent labels via the color's alpha channel).

The package is self-contained — the engine and reference catalogs are bundled in; only its real npm deps (commander, ink, react, zod) resolve on install.

Install

npm install -g djunker
djunker decode <code>          # now on your PATH

Or run it once without installing:

npx djunker decode <code>

Usage

Author a filter as a pipeline of small commands (a spec flows stdin → stdout), then encode. Rules are referenced by index or name; conditions by type (one of each per rule):

djunker draft create "Endgame" \
  | djunker draft rule create --action recolor --color '#80ff00ff' --name "Great 2H" \
  | djunker draft rule condition create rarity "Great 2H" --rarities Legendary,Unique \
  | djunker draft build            # → a base64 filter code

Decode any code back into a spec with djunker decode <code>. The command tree is self-describing for agents: djunker manifest (machine-readable command tree) and djunker schema (JSON Schema for the spec).

Launch the interactive terminal builder with djunker interactive.

Links

License

MIT