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

@gvnrdao/dh-lit-actions

v0.0.82

Published

Diamond Hands Protocol LIT Actions - Deterministic, Auditable Builds

Readme

dh-lit-actions: Diamond Hands LIT Actions Package System

A comprehensive, deterministic, and auditable build system for LIT Protocol Actions used in the Diamond Hands Protocol.

Architecture

lit-actions/
├── src/                          # LIT Action TypeScript sources
├── scripts/                      # Build, minify, upload scripts (TypeScript)
├── out/                          # Compiled .js files from src/
├── dist/                         # Minified, deployment-ready .action.js files
├── pkg-src/                      # Package source (registry + types)
└── pkg-dist/                     # Built npm package (dh-lit-actions)

Two-Phase System

Phase 1: LIT Actions Development & Deployment

  • Source: src/*.ts - TypeScript LIT Actions
  • Build: out/*.js - Compiled JavaScript
  • Minify: dist/*.action.js - Minified for IPFS deployment
  • Upload: Deploy to IPFS via Pinata

Phase 2: NPM Package Generation

  • Package Source: pkg-src/ - Registry and types
  • Package Build: pkg-dist/ - Compiled npm package
  • Package Name: dh-lit-actions - Published to npm

Commands

Development Commands

npm run clean          # Clean out/ and dist/
npm run build          # Build src/ → out/ (TypeScript compilation)
npm run minify         # Minify out/ → dist/ (deployment-ready)
npm run upload         # Upload dist/ to IPFS (mock mode by default)
npm run deploy         # Full deployment pipeline (clean + build + minify + upload)

Package Commands

npm run clean:pkg      # Clean pkg-dist/
npm run build:package  # Update registry + build pkg-src/ → pkg-dist/
npm run package        # Full package build (clean:pkg + build:package)
npm run release        # Complete release (deploy + package)

Environment Setup

  1. Copy the example configuration:

    cp .env.example .env
  2. Configure for your needs:

Mock Mode (Development - Default)

MOCK_MODE=true
DEBUG_BUILD=false

Production Mode (Real Pinata Upload)

PINATA_JWT=your_pinata_jwt_token_here
MOCK_MODE=false
DEBUG_BUILD=false

Getting Pinata JWT

  1. Go to Pinata Keys
  2. Create a new API key
  3. Select Admin permissions or at minimum:
    • pinFileToIPFS
    • pinJSONToIPFS
  4. Copy the JWT Token (not API Key/Secret)
  5. Add to your .env file as PINATA_JWT

Build Commands

# Clean build
npm run clean

# Build LIT Actions (with debug)
DEBUG_BUILD=true npm run build

# Upload to IPFS (mock mode)
npm run upload

# Build + Upload
npm run deploy

Mock Mode Quality

Our mock mode is very good for development:

  • Deterministic: Same content = same CID
  • Realistic Format: Proper IPFS CID format (Qm...)
  • Reproducible: Perfect for testing
  • Hash-based: Content integrity guaranteed
  • Offline Ready: No network dependencies

Mock CID Example: Qmd75a736b6ea15647bc551d8c55c6481acba3b2bcbc63

The mock system generates CIDs based on content hash, so:

  • Same TypeScript source → Same built JS → Same mock CID
  • Perfect for development and testing
  • Switch to real Pinata when ready for deployment