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

sipheron-vdr

v0.9.11

Published

This directory contains the Node.js Command Line Interface (CLI) source code. Contributor notes and architecture details are below.

Readme

SipHeron VDR — CLI Tool Reference

This directory contains the Node.js Command Line Interface (CLI) source code. Contributor notes and architecture details are below.

Architecture & Directory Structure

The CLI is built using Commander.js and handles all continuous integration (CI) and developer workflows for anchoring hashes to the blockchain.

  • src/index.js: The main entry point. Registers all commands via Commander and handles global error catching.
  • src/commands/: Subcommands for the CLI.
    • config.js: Manages local .vdr/config.json settings (apiUrl, network, API key).
    • login.js: Authenticates a user and securely stores their API key.
    • stage.js: Recursively scans a directory, calculate SHA-256 hashes for all files, and prepares them in a local staging file.
    • anchor.js: Reads the staged hashes, securely signs requests, and submits them to the backend API for Solana anchoring.
    • verify.js: Takes a local file, recalculates its hash, queries the Solana RPC, and cryptographic proves whether the hash exists and is valid on-chain.
    • batch.js: Monitors pending asynchronous bulk-anchor operations on the backend.
  • src/utils/: Utilities and core helpers.
    • configManager.js: Secures the CLI configuration. Critically, it encrypts the apiKey using an AES-256-GCM cipher derived from a machine-specific scrypt salt (combining OS hostname and username). This prevents simple token theft from the filesystem.
    • permissionValidator.js: Ensures that internal directories and staging files have strict 0600/0700 filesystem permissions to prevent cross-user snooping on shared CI runners.
    • hash.js: Node.js crypto wrappers for calculating deterministic SHA-256 hashes.
    • stagingManager.js: Handles the local state of files that have been hashed but not yet anchored.

Security Model

The CLI operates on a Zero-Knowledge principle. It never uploads source code or binary files to the backend server. All hashing (SHA-256) happens strictly locally on the user's machine or ephemeral CI runner. Only the 32-byte cryptographic hash string and the filename are transmitted via HTTPS to the SipHeron API.

Testing

Run the utility tests using:

npm test