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

@aws-sdk/checksums

v3.1001.0

Published

Checksum algorithms and flexible checksums middleware for the AWS SDK

Readme

@aws-sdk/checksums

NPM version NPM downloads

Checksum algorithms and flexible checksums middleware for the AWS SDK.

Standardized API

The following checksum API symbols are available.

import { Sha1, Sha256 } from "@aws-sdk/checksums/sha";
import { Md5 } from "@aws-sdk/checksums/md5";
import { Crc32, Crc32c, Crc64Nvme } from "@aws-sdk/checksums/crc";

Each follows an identical interface, the Smithy Checksum interface:

interface Checksum {
  update(chunk: Uint8Array): void;
  digest(): Promise<Uint8Array>;
  reset();
}

Bytes go into update, and the checksums comes out of digest.

Where possible, digest is non-destructive. That means you can digest to get a checksum, and then keep adding more data with update.

Some checksums accept initial seeds.

| Algorithm | Digest length | Non-destructive digest | Accepts secret (HMAC) | | --------- | ------------- | ------------------------ | --------------------- | | Sha256 | 32 bytes | ✅ (only without secret) | ✅ | | Sha1 | 20 bytes | ✅ (only without secret) | ✅ | | Md5 | 16 bytes | ✅ | ❌ | | Crc32 | 4 bytes | ✅ | ❌ | | Crc32c | 4 bytes | ✅ | ❌ | | Crc64Nvme | 8 bytes | ✅ | ❌ |

Selective API

By default, the canonically named checksum algorithms (above) will use the best implementation for your bundling or runtime environment, some of which use natively available implementations. All checksums have a pure JavaScript fallback. To use a specific implementation, you can use the following implementation-specific import symbols, but this is not recommended.

import {
  // SHA1
  Sha1Js,
  Sha1Node,
  Sha1WebCrypto,
  // SHA256
  Sha256Js,
  Sha256Node,
} from "@aws-sdk/checksums/sha";
import { Md5Js, Md5Node } from "@aws-sdk/checksums/md5";
import {
  // CRC32
  Crc32Js,
  Crc32Node,
  // CRC32C
  Crc32cJs,
  Crc32cNode,
  //CRC32NVME
  Crc64Nvme,
  Crc64NvmeJs,
} from "@aws-sdk/checksums/crc";

Sha1Node, Sha256Node, and Md5Node use the node:crypto lib.

Sha1WebCrypto uses subtle crypto but falls back to JS when buffered data exceeds 8 MB.

Crc32Node uses node:zlib.

Crc64Nvme uses the AWS CRT if you load @aws-sdk/crc64-nvme-crt.

What does the AWS SDK do with this package?

The AWS SDK uses Sha256 for Signature V4 signing, Crc32 for event stream message integrity, and all other algorithms are used for data integrity checksumming.