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

caesar

v1.1.12

Published

An easy-to-use advanced cryptography library.

Downloads

25

Readme

Caesar

An easy-to-use advanced cryptography library that lets you focus on writing applications that process data, not encrypted data.

  • Examples: https://github.com/Bren2010/caesar/tree/master/examples
  • Documentation: http://bren2010.github.io/caesar/

Install

npm install caesar

Currently Implemented

  1. Stream Ciphers (Confidential and/or Authenticated)
  2. Deterministic Authenticated Encryption (SIV-CTR)
  3. Disk Encryption (XTS)
  4. Searchable Symmetric Encryption (Single-User and Multi-User, Ranked)
  5. Commitments
  6. One-Time Signatures (HORS)
  7. Commitments to a Set (Merkle Trees)
  8. k-Time Signatures (MW-Chains)

Where I Ramble for a Bit

A lot of security officials will tell web developers that if they need to type the letters 'AES' then they're doing cryptography wrong. However, they rarely offer any actual secure options to help their audience complete that totally awesome NSA-proof application they've had in mind for the last couple of weeks. Combine this with the recent "Secure, Decentralized, and Anonymous {Insert Word Here} for Everyone!" fetish, and there has been astonishing amount of cryptographic code written recently that is not only difficult to peer review, but often buried within an application's core instead of left somewhere conspicuous. While this newfound affinity for cryptography is fantastic, not every one of these developers will want to dedicate the time and effort required to build a secure product before slapping on the label "It uses cryptography!" Or, perhaps even more disconcertingly, not every one of these developers is aware of the true power of modern cryptography.

My goal in writing this library is to provide simple and easy-to-use interfaces to advanced cryptographic tools in such a way that someone with no prior knowledge of them can correctly integrate them in their own applications with as little effort as possible. That way they can focus on what they love (developing) and I can focus on what I love (cryptography).

Some things that might be added in the future include: user authentication, more complex key exchanges, zero-knowledge proofs, and homomorphic encryption schemes, poker.

I've tried to keep all of the code very well documented and write examples that concisely demonstrate proper use of the library. If you encounter any problems or confusion while using the library, please open an issue ~~or send me an email~~.