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

weld-env

v0.1.0

Published

Push and pull encrypted .env files with your Weld workspace

Readme

weld-env

Push and pull encrypted .env files with your Weld workspace.

Install

npm install -g weld-env

Quick start

# 1. Log in (generates a token from the Weld web app → Settings → CLI Tokens)
weld login

# 2. Link your project directory to a workspace
cd my-project
weld init

# 3. Pull the team's .env
weld pull

# 4. Make changes and push
weld push

Commands

| Command | Description | |---|---| | weld login | Authenticate with your Weld workspace | | weld logout | Remove saved credentials | | weld whoami | Show the currently logged-in user | | weld init | Link this directory to a Weld workspace | | weld pull | Download + decrypt .env from Weld | | weld push | Encrypt and upload .env to Weld | | weld status | Show sync status without decrypting |

Options

weld pull --output .env.local    # write to a different file
weld push --input .env.staging   # push from a different file
weld push --no-retry             # disable automatic conflict retry

How it works

All encryption happens locally on your machine. The Weld server only stores ciphertext it cannot read. Your passphrase never leaves your machine.

Security model

  • Zero-knowledge encryption — the server only stores ciphertext
  • Argon2id key derivation — your passphrase is stretched via Argon2id before deriving your device keypair
  • Per-device Curve25519 keypairs — each machine has a unique keypair derived from your passphrase + a device-specific salt
  • DEK wrapping — the Data Encryption Key is sealed separately for each device using crypto_box_seal
  • Signed pushes — every push is BLAKE2b-signed with your private key

Requirements

  • Node.js ≥ 18
  • A Weld workspace with Env Sync initialized