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

@wishknish/knishio-kcore

v0.2.1

Published

Node binding of kcore, the KnishIO shared crypto core (SHAKE256, WOTS+, ML-KEM-1024/768): N-API prebuilds with a WebAssembly fallback.

Readme

@wishknish/knishio-kcore

Node binding of kcore (KnishIO-Crypto-Core 0.2.1), the shared C crypto core of the KnishIO SDKs: SHAKE256, WOTS+ chains and the WOTS+ address, and ML-KEM-1024 / ML-KEM-768 (FIPS 203, on mlkem-native v1.2.0).

The KnishIO JavaScript and TypeScript SDKs list this package as an optional dependency and use it when it loads; without it they run their pure-JS paths with byte-identical results.

Backends

| backend | what loads | when | |---|---|---| | napi | prebuilds/<target>/kcore.node, kcore statically linked into a Node-API addon | linux-x64-gnu, linux-arm64-gnu (glibc ≥ 2.17), linux-x64-musl, linux-arm64-musl, darwin-universal (macOS ≥ 11, arm64 + x86_64), windows-x64 | | wasm | kcore.wasm (no imports), instantiated synchronously | any other platform, or when the prebuild fails to load |

KNISHIO_KCORE_BACKEND = auto (default: napi, then wasm), napi or wasm, read once at load. If no backend loads, require('@wishknish/knishio-kcore') throws. Node ≥ 20. The package has no dependencies and no install scripts.

API

const kcore = require('@wishknish/knishio-kcore') // or: import kcore from '@wishknish/knishio-kcore'

| export | | |---|---| | backend, libraryPath, kcoreVersion, abiVersion() | what loaded; kcore 0.2.1, ABI 1 | | shake256(input: Uint8Array, outLen: number): Uint8Array | SHAKE256, outLen 1..1048576 bytes | | chainsHex(chunks: string, counts: number[]): string | advances counts.length WOTS+ chains of 128 hex characters each, counts[i] steps (0..64) of hex(SHAKE256(chunk, 64 bytes)) | | wotsAddress(key: string): string | WOTS+ address (64 hex) of a 2048-hex key | | wotsAddressV2(key: string): string | WOTS+ address (64 hex) of an 8192-hex (64-chain) key | | mlkemKeypair(set, seed) → { publicKey, secretKey } | deterministic keypair from a 64-byte seed | | mlkemEncaps(set, publicKey, coins) → { cipherText, sharedSecret } | coins must be 32 fresh random bytes on every call: reusing them against one key repeats the ciphertext and the shared secret | | mlkemDecaps(set, cipherText, secretKey) → Uint8Array | 32-byte shared secret |

set is 1024 or 768. Byte results are plain Uint8Arrays. Errors carry a code: KCORE_BAD_ARG (TypeError: type or length), KCORE_BAD_SET (RangeError), KCORE_REJECTED (kcore rejected the input: a count outside 0..64, a NUL byte, a public key failing the FIPS 203 check).

Building from source

npm ci --ignore-scripts
node scripts/fetch-kcore.mjs all          # sha256-pinned kcore Release packages -> vendor/, kcore.wasm
bash scripts/build-addon.sh <target>      # zig 0.16.0 (linux-*, windows-x64) or Xcode clang (darwin-universal)
npm test                                  # KNISHIO_KCORE_BACKEND=wasm npm test for the fallback

License

GPL-3.0-or-later, as kcore (LICENSE). The binaries also contain mlkem-native v1.2.0, whose license text ships as LICENSE-mlkem-native (copied from the pinned submodule in the kcore 0.1.0 source release).