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

sealbox

v1.10.14

Published

Discreet network traffic encryption with ephemeral keys and end-to-end security

Downloads

6

Readme

sealbox

Secure your network data easily. We encrypt everything so no one can read or mess with it while it travels.

Install

npm install sealbox

How to use (Automatic)

1. Server (Receives data)

const { CipherTransport } = require('sealbox');
// In a real app, generate these once and save them securely!
const ECDH = require('sealbox/src/crypto/primitives/ecdh'); 

async function startServer() {
  const keys = await ECDH.generateKeyPair();
  const SERVER_PRIVATE_KEY = keys.privateKey;
  const SERVER_PUBLIC_KEY = keys.publicKey; 
  
  console.log("Give this Public Key to the client:", SERVER_PUBLIC_KEY);

  // When you get a request:
  async function onReceive(encryptedData) {
    const transport = new CipherTransport();
    // Unlocks the data automatically
    try {
        const opened = await transport.open(encryptedData, SERVER_PRIVATE_KEY);
        console.log("Decrypted Message:", JSON.parse(opened.toString()));
    } catch (err) {
        console.error("Security warning: Data was tampered with!");
    }
  }
}
startServer();

2. Client (Sends data)

const { CipherTransport } = require('sealbox');

// Paste the Server's Public Key here
const SERVER_PUBLIC_KEY = `...`; 

async function send() {
  const transport = new CipherTransport();
  
  const myData = { password: "super_secret", id: 123 };

  // Locks the data automatically using the Server's Public Key
  const box = await transport.seal(myData, SERVER_PUBLIC_KEY);
  
  // Send 'box' to your server (e.g., via fetch or axios)
  console.log("Ready to send:", box.toJSON());
}
send();

Why use this?

It handles all the complex math for you. It ensures:

  1. Privacy: Only the server can read the data.
  2. Safety: If someone changes the data, the server rejects it.
  3. Simplicity: No need to manage session keys manually.

Deep Packet Inspection (DPI) View

If a network administrator or hacker inspects the packet (DPI), they will not see your JSON data. They will only see an opaque, random-looking structure like this:

{
  "v": "1",
  "k": "04a2...b7c9", 
  "i": "8f3a...1d4e",
  "c": "a1b2c3d4e5...9988776655", 
  "t": "f1a2...b3c4"
}
  • v: Version of the protocol.
  • k: Ephemeral Public Key (harmless to share).
  • i: Initialization Vector (randomness for the cipher).
  • c: Ciphertext (Your actual data, fully encrypted).
  • t: Auth Tag (Ensures nobody tampered with the data).

License

MIT