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

@armadoc/crypto

v0.2.1

Published

The end-to-end encryption core shared by the Armadoc web app and CLI

Readme

@armadoc/crypto

The end-to-end encryption core of Armadoc, shared by the web app and armadoc. Runs anywhere globalThis.crypto does: modern browsers and Node 24+.

  • Each file is sealed under a fresh AES-256-GCM key; the payload is the 12-byte IV followed by the ciphertext.
  • That key is wrapped with RSA-OAEP (SHA-256, 2048-bit) once per key the recipient has enrolled, and each wrap names its key.
  • Opening picks the wrap made for a locally held key. A file sent before that key was enrolled has no such wrap, which reads as PrivateKeyNotFoundError, distinct from a DecryptionError.

The core holds no keys and does no I/O; storage and the network belong to the client.

import {
  decryptPayload,
  generateKeyPair,
  importPublicKey,
  pickWrap,
  sealFile,
  unwrapFileKey
} from '@armadoc/crypto'