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

argon2-wasm-pro

v1.1.0

Published

Argon2 library compiled for browser runtime

Downloads

54

Readme

Build Status

argon2-wasm

https://github.com/P-H-C/phc-winner-argon2 compiled to base64,It works in both the NodeJS environment and the browser environment.

This project does not need to reference annoying ".wasm" files when used under the browser.

usage

install:

npm install argon2-wasm-pro

Add script:

const argon2 = require('argon2-wasm-pro');

Get hash:

argon2
  .hash({ pass: 'password', salt: 'somesalt' })
  .then(h => console.log(h.hash, h.hashHex, h.encoded))
  .catch(e => console.error(e.message, e.code));

Verify the encoded hash:

argon2
  .verify({ pass: 'password', encoded: 'enc-hash' })
  .then(() => console.log('OK'))
  .catch(e => console.error(e.message, e.code));

Bring your own bundler and promise polyfill. Other parameters:

argon2
  .hash({
    // required
    pass: 'password',
    salt: 'salt',
    // optional
    time: 1, // the number of iterations
    mem: 1024, // used memory, in KiB
    hashLen: 24, // desired hash length
    parallelism: 1, // desired parallelism (will be computed in parallel only for PNaCl)
    type: argon2.ArgonType.Argon2d, // or argon2.ArgonType.Argon2i
    distPath: '' // asm.js script location, without trailing slash
  })
  // result
  .then(res => {
    res.hash; // hash as Uint8Array
    res.hashHex; // hash as hex-string
    res.encoded; // encoded hash, as required by argon2
  })
  // or error
  .catch(err => {
    err.message; // error message as string, if available
    err.code; // numeric error code
  });

Building

Prerequesties:

  • emscripten with WebAssembly support (https://webassembly.org/getting-started/developers-guide/)
  • CMake