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

sha256d

v1.0.0

Published

double sha256

Readme

sha256d

double sha256.

Example

var sha256d = require('sha256d')

var hash = sha256d().update('hello', 'ascii').digest('hex')
console.log(hash)
//9595c9df90075148eb06860365df33584b75bff782a510c6cd4883a419833d50

why

sha1 is no longer considered secure, and should not be used in new cryptosystems. recent attacks have been developed which weaken sha1 significantly, from 2^80 to 2^69 attempts to find a collision.

Schiener estimates that by 2021 it could cost as little at 41k usd to generate a sha1 collision.

Also, Merkle–Damgård constructions, such as the sha1 and sha2 family of algorithms also are succeptable to a length-extension attack. this means that if you know x = sha(y) you can calculate x2 = sha(y + z) without knowing y.

This may or may not be a problem in your system, but there is no harm in being belt and suspenders safe.

License

MIT