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

saro-dat-es6

v2.0.1

Published

Distributed Access Token

Downloads

23

Readme

DAT - Distributed Access Token

NPM

saro-dat

DAT

# Example
signature_algorithm: P256
crypto_algorithm: AES128GCMN
plain: 123
secure: asdf

# DAT result Example
1776530737.11.MTIz.8yKUvzs7mg3tDwdeA9I2gNOliewpTgm9OVbEY3Qh6io.qfnqmXKuNE3MfRr576rxNMCchxbY1iqC07-woJcbCudt2O0BAyK_86ypaSfLJjkGq9FZxpGrsgBDkk-xQhGvmA

expire.kid.plain.secure.sign

  • expire: number
    • Unix-Timestamp (sec)
  • kid: stringifiable
    • key id
  • plain: base64 url no pad
    • Text Data
  • secure: base64 url no pad
    • Encrypted Text Data
  • sign: base64 url no pad
    • dat-bank[kid].sign(expire.kid.plain.secure)

DAT KEY

# Example
1.2.P256.DErFl-U5h4fdbnAXTTs2GikkJgZwYXV25v2EdFeXIXs.AES128GCMN.5VEziIzCu2LRsK1XS6OYxA.1776541326.1776544626.1800

version.kid.signature-algorithm.signature-key.crypto-algorithm.crypto-key.issue-begin.issue-end.token-ttl

  • version: number
    • dat-key format version
  • kid: stringifiable
    • key id
  • signature-algorithm: text
    • sign algorithm
  • signature-key: base64 url no pad

    The signature-key is categorized into three types: FULL (signing-key~verifying-key), SIGNING (signing-key), and VERIFYING (~verifying-key).

    Whether a key is for sign or verify can be distinguished by the presence of a leading tilde (~). Generally, if you output the sign key alone, the public key can be derived from it (using the private key). However, depending on the platform, this derivation feature may not be available; in such cases, you should output the full key and parse it for use.

    • FULL: <signing key base64>~<verifying key base64>
    • SIGNING: <signing key base64>
    • VERIFYING: ~<verifying key base64>
  • crypto-algorithm: text
    • crypto algorithm,
  • crypto-key: base64 url no pad
    • crypto key
  • issue-begin: number
    • issue begin time
  • issue-end: number
    • issue end time
  • token-ttl: number
    • token(dat) TTL

support signature algorithm

| name | algorithm | |--------|------------| | P256 | secp256r1 | | P384 | secp384r1 | | P521 | secp521r1 |

support crypto algorithm

| name | algorithm | |------------|-----------------------------| | AES128GCMN | aes-128-gcm n(nonce + body) | | AES256GCMN | aes-256-cbc n(nonce + body) |

See Also