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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@doctormckay/crypto

v1.2.0

Published

An implementation of Node's crypto

Downloads

3

Readme

McCrypto

As with everything in the @doctormckay namespace on npm, this is mostly for my own usage. If you want to use it that's fine, but don't expect any support. I'll respect semver so you don't need to worry about breaking changes if you pin your dependencies properly.

This is just a module that uses node's built-in crypto module. The idea is to make it easier to encrypt stuff and store it on disk or send it over the wire securely.

See here for the supported ciphers.

Methods

isWellFormed(buffer)

  • buffer - A Buffer object

Returns true if the input buffer is a well-formed blob which can be decrypted by this module.

encrypt(cipher, key, data)

  • cipher - One of the Cipher constants
  • key - Either a string or a Buffer containing your encryption key
  • data - Either a string (interpreted as UTF-8) or a Buffer containing the plaintext you want to encrypt

Returns a Buffer containing the encrypted contents. The output should be interpreted as a black box, but for reference here is the structure:

  • magic - A 2-byte magic value
  • flags - A 1-byte bitstring of flags
  • cipher - A 1-byte value containing the cipher constant

All remaining data is left up to the specific cipher.

  • AES256CTRWithHMAC
    • ivLength - A 1-byte value containing the length of the IV
    • iv - The randomly-generated binary IV (length given by ivLength)
    • ciphertext - The encrypted ciphertext
    • hmac - The HMAC (20 bytes)

The key may be interpreted differently depending on the cipher.

  • AES256CTRWithHMAC - The key is hashed with SHA256 and the binary hash is used as the key

decrypt(key, data[, expectAuthentication])

  • key - Either a string or a Buffer containing your encryption key (should match what was given to encrypt())
  • data - A Buffer containing your encrypted data (should be identical to what was returned by encrypt())
  • expectAuthentication - Optional. If true, this will throw an Error if the data is not authenticated (e.g. with HMAC)

Decrypts a buffer and returns the plaintext. If you originally passed a string to encrypt(), this will return a UTF-8 string. Otherwise, it will return a Buffer.