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

@m2c/core

v0.11.0

Published

Shared protocol primitives (HMAC signing, error taxonomy, money) for the M2C SDKs.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

m2cmarketsm2cmarkets

Keywords

m2cpaymentshmacsdk

Readme

@m2c/core

Shared protocol primitives for the M2C SDKs. You normally do not depend on this directly - use @m2c/server (merchant backend) or @m2c/vendor (payment vendor), which build on it.

It exists so the security-sensitive parts of the protocol have exactly one implementation:

  • sign(secret, body, { timestampSeconds? }) - produce the X-M2C-Signature / X-M2C-Timestamp pair (HMAC-SHA256 over timestamp + "\n" + body).
  • verify(secret, body, signature, timestamp, { maxSkewSeconds?, nowSeconds? })
    • constant-time verification with the full failure taxonomy.
  • M2CError / M2CSignatureError (with a reason: missing | incomplete | malformed | timestamp_skew | mismatch | empty_secret).
  • getHeader, the header-name constants, and the skew default.
  • MIN_MONETARY_VALUE / MAX_MONETARY_VALUE + assertMonetaryAmount for the major-units-at-the-wire boundary check.
  • parseRetryAfter, isLoopbackHost, and assertSecureBaseUrl for the shared HTTP transport policy used by the server and vendor SDKs.
  • readBoundedResponseBody for timeout-aware response consumption with a 64-KiB memory bound.

Zero runtime dependencies (built on node:crypto). Requires Node 18+.

The malformed-vs-missing distinction is part of the protocol contract: a malformed-but-present signature is a tampering signal and must always be rejected. Every M2C SDK and the M2C server share this behavior, anchored by a known-answer test vector asserted in every suite.