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

@kaditang/quantum-exposure

v0.3.0

Published

Is your wallet quantum-exposed? Check whether an Ethereum, Bitcoin, or Solana address has already revealed its secp256k1 public key on-chain (harvest-now-decrypt-later), how much is at risk, and whether it's migratable in place. Free, zero-dep, public RPC

Readme

quantum-exposure

npm ci license

Is your wallet quantum-exposed? One command tells you whether your Ethereum, Bitcoin or Solana address has already revealed its public key on-chain — and is therefore a harvest-now, decrypt-later target for a future quantum computer.

npx @kaditang/quantum-exposure 0xYourAddress      # Ethereum
npx @kaditang/quantum-exposure bc1p…              # Bitcoin (Taproot, P2PKH, segwit…)
npx @kaditang/quantum-exposure <solana-address>   # Solana (the address IS the pubkey)

No install needed — or try the hosted page: 402sentinel.com/quantum.

  ⛔  0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045
  Public key EXPOSED — 5.6948 ETH at risk.
  signals: exposed=true | outgoing_txs=5898 | balance=5.6948 ETH | at_risk=5.6948 ETH
  → Move funds to a FRESH address you have never spent from, single-use until PQC wallets ship.

Why this matters

Ethereum signs with secp256k1 (ECDSA), which Shor's algorithm breaks on a large enough quantum computer. The catch specific to blockchains: the ledger is permanent and public, so harvest now, decrypt later is trivial. But your public key is hidden behind your address hash until the first time you SEND a transaction — the signature then reveals it forever.

So the single most important question for any address is: has its key been exposed yet, and how much is sitting behind it? That's what this checks.

What it reports

| decision | meaning | | --- | --- | | ✅ safe-for-now | Never spent → public key still hidden. Quantum-safer; keep it cold. | | ⛔ exposed | Has spent + holds funds → key is public, funds harvestable. Migrate. | | 🟡 exposed-empty | Key public but ~0 balance → nothing at risk now; don't reuse it. | | 🔄 smart-account | Contract / no single EOA key → migratable in place via account abstraction. |

Handles EIP-7702 correctly: a delegated EOA still has an exposed secp256k1 key (it's not a contract), but it gains signature agility to delegate to a post-quantum verifier.

Use it in code

import { scan, scanAddress, scanBitcoin, classify } from "@kaditang/quantum-exposure";

await scan("0x…");        // auto-dispatches: Ethereum (0x…) vs Bitcoin
await scan("bc1p…");      // Bitcoin — Taproot, P2PKH, P2WPKH, P2SH, P2WSH
// or classify from your own data (no network):
classify({ outgoingTxs: 42, balanceEth: 3, code: "0x" });

Ethereum (via a public RPC) — handles EIP-7702 delegated EOAs. Bitcoin (via mempool.space) — Taproot (bc1p) outputs are exposed by design; other types expose the key only once spent from. Solana (via a public RPC) — the address is a 32-byte Ed25519 public key, so a normal wallet is exposed from creation (no "never-spent = safe" state); program-derived / token accounts have no keypair. Set ETH_RPC / BTC_API / SOL_RPC to use your own nodes.

Not panic — planning

A cryptographically-relevant quantum computer is not imminent (current estimates put it around the end of the decade). This is a planning tool: know your exposure now, so migration is a choice and not a fire drill. Informational, not financial advice.

Built by the team behind 402Sentinel — on-chain risk gates for the agent economy.