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

webcrypto

v0.1.1

Published

Use the Node.js crypto module API without having to worry if it is being run in browser or Node.js

Downloads

18,644

Readme

webcrypto

Coverage Status Travis CI Circle CI Dependency Status js-standard-style

WebCryptoAPI polyfil to work in Node.js in the Browser (so that you don't have to be concerned about moving crypto code between a browser and server side app)

Roadmap

  • [x] Expose the Node.js crypto module interface
  • [x] Use crypto-browserify to make it work in the browser
  • [ ] Replace crypto-browserify with WebCryptoAPI when browser supports it
  • [ ] Consider if we should replace the functions that TweetNaCL offers for perf/or and stability improvements

API

This module should follow at all times the Node.js Crypto API https://nodejs.org/api/crypto.html

Tests

This module is using tests from crypto-browserify to validate that the expectations remain fulfilled