On 29 October 2026, KXCO published 15 releases of 14 post-quantum packages on npm, every one with an SLSA provenance attestation. The core library, kxco-post-quantum 1.13.0, adds a self-testing entry point designed against the FIPS 140-3 Level 1 software requirements, and its code passed all 3,522 test cases NIST's Demo test server graded, with zero failures. The HSM package, kxco-pq-hsm, can now keep ML-KEM keys on a PKCS#11 v3.2 token. The scanner, kxco-pq-scan 1.4.0, stamps every quantum-vulnerable finding with the dates in NIST IR 8547.

Apart from the core library itself and the scanner, which has no dependencies, the latest release of each package requires kxco-post-quantum 1.13.0. KXCO's post-quantum page calls these packages "the cryptography that KXCO's products are built on".

This post sets out what changed, package by package, how each capability works, how it relates to each of the 8 KXCO products, and how to check the packages from a terminal.

The releases

Each line gives the package, the version published on 29 October 2026, and what changed. The times are the npm registry's, in UTC.

  • kxco-pq-hsm 1.9.0 (00:43) can generate and decapsulate ML-KEM keys on a PKCS#11 v3.2 token.
  • kxco-post-quantum 1.13.0 (01:21) adds the self-testing entry point, kxco-post-quantum/fips.
  • kxco-pq-scan 1.4.0 (07:49) puts the NIST IR 8547 dates on findings and in the CBOM, and names crypto-js's weak algorithms.
  • Identity and signing (07:50 to 07:52): kxco-pq-attest 2.3.1, kxco-pq-sdk 2.4.2, kxco-pq-agent 1.4.1, kxco-pq-cli 2.4.2 and kxco-pq-hsm 1.9.1 each now require kxco-post-quantum 1.13.0.
  • Records, channels and the chain (07:49 to 07:50): kxco-pq-audit 1.6.1, kxco-pq-network 1.2.1, kxco-pq-chain 2.4.2, kxco-pq-tls 2.0.1, kxco-pq-vault 2.0.1 and kxco-post-quantum-webhook 1.4.1 each now require kxco-post-quantum 1.13.0.
  • kxco-pq 3.0.1 (07:58) is the one-install package, with every dependency at its 29 October version.
EXHIBIT 1What one installbringskxco-pq 3.0.1 and the packages itinstalls, each at its 29 October2026 release. Each one beside thecore requires kxco-post-quantum1.13.0.kxco-pq 3.0.1one install, 11 moreKXCO packageskxco-post-quantum 1.13.0ML-DSA, ML-KEM and SLH-DSA,self-testing entry pointkxco-pq-sdk 2.4.2institution identitykxco-pq-hsm 1.9.1can hold ML-DSA andML-KEM keys on the tokenkxco-pq-attest 2.3.1signed envelopeskxco-pq-audit 1.6.1signed audit logkxco-pq-network 1.2.1three levels of verificationkxco-pq-chain 2.4.2Armature verifies thesignature in consensuskxco-pq-tls 2.0.1encrypted channels,ML-KEM-1024 with X25519kxco-pq-vault 2.0.1file encryption,ML-KEM-1024 by defaultkxco-pq-agent 1.4.1signing keys for AI agentskxco-post-quantum-webhook 1.4.1signed webhooksa package on 1.13.0the core librarythe one installSource: npm registry and a freshinstall of kxco-pq 3.0.1 in Node26 on Linux, 29 October 2026;functions as kxco.ai/post-quantumand the package READMEs describethem.29 October 2026KXCO.ai

Ahead of the deadlines: NIST IR 8547

NIST published the final version of IR 8547, Transition to Post-Quantum Cryptography Standards, in October 2026. Three passages matter most to anyone who supplies cryptography to an institution.

  • The end date. "NIST will deprecate all quantum-vulnerable cryptography after 2030 and disallow its use under NIST standards and guidelines after 2035."
  • The federal deadline. Executive Order 14412 and OMB Memorandum M-26-15 require the government's most sensitive systems to adopt post-quantum cryptography for key establishment by 31 December 2030, and for digital signatures by 31 December 2031.
  • SHA-1. It "is currently deprecated for all remaining technical applications and will be disallowed for use in FIPS-validated cryptographic modules after 2030."

KXCO's packages supply both today: ML-KEM for key establishment and ML-DSA for signatures, the FIPS 203 and FIPS 204 standards. Five of them default to the strongest sets, the Category 5 sets that CNSA 2.0 names: kxco-pq-tls and kxco-pq-vault use ML-KEM-1024, and kxco-pq-sdk, kxco-pq-agent and kxco-pq-hsm use ML-DSA-87. IR 8547 recommends ML-KEM-768 as the general default and other sets "when higher security is required": ML-KEM-1024 is the higher-security set.

An institution working to those dates needs evidence that its cryptography is correct, keys held in hardware it controls, and a starting point for the inventory of what it has to replace. The three capabilities below address each of them.

The self-testing entry point

kxco-post-quantum/fips is a separate entry point in kxco-post-quantum 1.13.0 for deployments that want the cryptography inside one fixed, self-testing module. It is designed against the FIPS 140-3 Level 1 software requirements.

  • A fixed boundary. Its folder, src/fips, carries its own copy of the noble code and loads nothing from the rest of the package.
  • A NIST SP 800-90A random bit generator. An HMAC_DRBG with SHA-512, seeded from /dev/urandom, supplies every random value.
  • The integrity test first. Every file is checked against a manifest signed with the ML-DSA-87 release key before any service loads.
  • Self-tests. The known answers come from NIST's own ACVP vectors, and a pairwise test runs on every generated key pair.
  • An error state. Any failure leaves every service refused until the process restarts.

It offers ML-KEM-768, ML-KEM-1024, ML-DSA-65 and ML-DSA-87. It runs on Node.js, needs /dev/urandom, and has been tested on Linux. The package's README gives the calls in order:

  • Check that fips.status().state reads operational, and stop on its reason if it does not.
  • Generate a key pair with fips.generateKeypair('ML-DSA-87'), and store the seed it returns: the seed is the key.
  • Sign and verify with fips.sign and fips.verify, under the same context string.
  • Wipe the secret key and the seed with the entry point's own wipe call when they are no longer needed.

What NIST's Demo server graded

NIST's Demo test server graded the entry point's code in session 783228, created on 28 October 2026: 3,522 test cases across 13 vector sets, all passed. They covered ML-KEM key generation, encapsulation and decapsulation, ML-DSA key generation, signing and verification, SHA2-256 and SHA2-512, SHA3-256 and SHA3-512, SHAKE-128 and SHAKE-256, HMAC-SHA2-512 and the HMAC_DRBG random bit generator.

The results are published in the repository, one disposition file per vector set, with the environment they ran in: Node.js 26.12.1 on Debian 13, Linux x64. A draft Security Policy is published beside the code in the structure of NIST SP 800-140B. The packages also rest on KXCO's published evidence document: 1,793 NIST ACVP test vectors passed, 225 interoperability checks against liboqs, Bouncy Castle and the Python reference implementations, in both directions, with zero failures, and tarballs that rebuild byte for byte from their own tags. The entry point has not yet been through a laboratory or NIST's certification programme.

ML-KEM keys on the token

kxco-pq-hsm already generated ML-DSA-87 and ML-DSA-65 keys on a PKCS#11 token and signed there. From 1.9.0 it does the same for ML-KEM, so both halves of the post-quantum toolkit can now run on the token. Set the option mlKemMechanism to 0x17, which is CKM_ML_KEM, and the backend generates ML-KEM-1024 and ML-KEM-768 keys on the token with C_GenerateKeyPair and decapsulates there with the PKCS#11 v3.2 call C_DecapsulateKey.

The private object is marked CKA_SENSITIVE and not CKA_EXTRACTABLE, so the private key never enters the process. The 32-byte shared secret does, because returning it is what decapsulation is for.

  • Proof before the claim. The decapsulationMode property reads on-token only after a decapsulation on the token has matched an encapsulation to its public key.
  • A refusal at start. The backend's open() call refuses to start if the token does not offer both ML-KEM mechanisms.
  • Earlier keys still work. Keys wrapped before the option was set keep decapsulating in the process.

kxco-pq-hsm's integration tests prove the path against kryoptic, a PKCS#11 v3.2 software token, on Linux x86_64.

NIST dates in the scanner

kxco-pq-scan reads a project's package-lock.json and reports which dependencies use cryptography a quantum computer breaks. Version 1.4.0 adds the IR 8547 dates to every quantum-vulnerable finding.

KXCO ran it on a hand-written example lockfile on 29 October 2026, with npx kxco-pq-scan@1.4.0. The report listed four quantum-vulnerable packages, among them jsonwebtoken and ecdsa-sig-formatter, under one line: "NIST IR 8547: NIST will deprecate these after 2030 and disallow them after 2035."

  • In the JSON output. Each finding carries a nist field with the document's name and the two years, 2030 and 2035. The package exports the same values as NIST_IR_8547.
  • In the CBOM. Every quantum-vulnerable algorithm in the CycloneDX 1.6 cryptography bill of materials, RSA and the elliptic curves, carries the property kxco:pq-scan:nistTransition with the two dates. Symmetric, hash and post-quantum algorithms carry none, apart from SHA-1, which carries IR 8547's note on its 2030 cut-off.
  • crypto-js, in full. crypto-js 4.2.0 ships md5.js, sha1.js, rc4.js and tripledes.js beside AES and SHA-2, and npm marks it no longer maintained. The scanner now names all four, declares each in the CBOM, and gives SHA-1 the IR 8547 note on its 2030 cut-off.

How each product relates

KXCO describes these packages as the cryptography its products are built on. Three products relate to the upgraded packages directly. Portcullis's free scanner is kxco-pq-scan. Herald issues identities and signatures, and four upgraded packages do identity and signing in code. Armature is where kxco-pq-chain writes and whose anchors kxco-pq-network checks. Every link between products below is stated on a KXCO product page and described as live, designed or in development as that page marks it. Every status is copied from the product's own page.

EXHIBIT 2The upgraded packagesand the 8 productsThe 3 products the upgradedpackages relate to directly, and 3of the links KXCO marks livebetween its products. The dashedlink is in development. Athanor,the KXCO engineering lab, is aninternal facility.Portcullisits free scanner,kxco-pq-scan, now datesevery quantum-vulnerablefindingLive in partsRound Tablecan read Portcullisfindings and HeraldattestationsLive, private deploymentsHeraldidentity and signatures.Four upgraded packagesdo identity and signingin code.Live for domains, documents,people and agentsArmaturechecks ML-DSA-87 andML-DSA-65 on chain.kxco-pq-chain writesto it.LiveSovereignsettles on Armature.Licensed institutionshold assets. KXCOsupplies the software.LiveGuildhallsettlement can useSovereign or theMember's owncustodianLiveHansedesigned to run onSovereignIn developmentAthanorthe KXCO engineering labInternal facilitya producta foundationan internal facilitya link that is live todaya link in developmentSource: kxco.ai/products and theseven product pages, read 29October 2026; KXCO for Athanor;npm registry.29 October 2026KXCO.ai

Portcullis, live in parts

Portcullis finds quantum-vulnerable cryptography across an estate. Its free scan is kxco-pq-scan. When version 1.4.0 finds quantum-vulnerable cryptography, its report gives the year NIST will deprecate it and the year NIST will disallow it, and its JSON output stamps each finding with both. Portcullis attestations are anchored on Armature.

Round Table, live, private deployments

Round Table sits at the centre. It can read findings from Portcullis and attestations from Herald as sourced claims.

Herald, live for domains, documents, people and agents

Herald is identity and signatures, and KXCO anchors its credentials on Armature. Four upgraded packages do identity and signing in code, and each release requires kxco-post-quantum 1.13.0:

  • kxco-pq-attest 2.3.1 signs any payload into a self-contained envelope a counterparty can check.
  • kxco-pq-sdk 2.4.2 issues institution identity with ML-DSA-87 keys by default and can sign through kxco-pq-hsm, which can now hold ML-KEM keys on the token as well as ML-DSA keys.
  • kxco-pq-agent 1.4.1 gives AI agents ML-DSA-87 signing keys by default, linked to the institution that sponsors them.
  • kxco-pq-cli 2.4.2 generates, fingerprints and rotates keys from a terminal.

Herald is designed to supply the identity of the parties in a Guildhall room, the senders and receivers in Hanse, and the signer of a Portcullis release.

Armature, live

Armature is the post-quantum settlement network and public record. It checks ML-DSA-87 and ML-DSA-65 signatures on chain and attests each finalised block with ML-DSA-87. Both Armature-facing packages moved onto 1.13.0. The first, kxco-pq-chain 2.4.2, posts signed intents for Armature to verify in consensus, and its test suite checks the operation tags it derives against the contract deployed on Armature. The second, kxco-pq-network 1.2.1, checks an envelope at three levels: the signature, the Armature anchor it carries, and a live answer from KXCO's key registry that the signing key is still trusted.

Sovereign, live

Sovereign is software for holding and moving value, and it settles on Armature. Licensed institutions hold assets. KXCO supplies the software.

Guildhall, live

Guildhall is where Members run their deals. Settlement can use Sovereign or the Member's own custodian, and Round Table Review supports larger transactions.

Hanse, in development

Hanse is designed to run on Sovereign, with Herald identities for senders and receivers and Armature for the record. No launch date is set.

Athanor, internal facility

Athanor is the KXCO engineering lab.

Check it yourself

Three commands, run from a terminal without an account, scan your own project, install the packages and check their signatures:

  • npx kxco-pq-scan scans the JavaScript dependencies of the project in the current folder.
  • npm install kxco-pq@3.0.1 installs kxco-pq and 11 more KXCO packages at their 29 October versions.
  • npm audit signatures checks the registry signatures and provenance attestations of everything installed.

KXCO ran the install in Node.js 26.12.1 on Debian 13 on 29 October 2026. The self-testing entry point reported operational, an ML-DSA-87 signature verified, and an ML-KEM-1024 key exchange produced matching secrets on both sides.

Questions

What did NIST's Demo test server grade?

The code of kxco-post-quantum/fips, the self-testing entry point. All 3,522 test cases in session 783228 passed, with zero failures, across 13 vector sets for ML-KEM, ML-DSA, SHA-2, SHA-3, SHAKE, HMAC and the random bit generator.

Which algorithms does the entry point offer?

ML-KEM-768 and ML-KEM-1024 for key establishment, and ML-DSA-65 and ML-DSA-87 for signatures. Every random value comes from its own HMAC_DRBG with SHA-512.

Will on-token ML-KEM work with my HSM?

It needs a token that offers PKCS#11 v3.2 ML-KEM: the CKM_ML_KEM and CKM_ML_KEM_KEY_PAIR_GEN mechanisms and the C_DecapsulateKey call. The backend refuses to start on a token that does not offer both mechanisms.

How do I take the upgrade?

Install kxco-pq 3.0.1 to take kxco-pq and 11 more KXCO packages at once, or raise the version of the one package you use. The latest release of every package that builds on the core requires kxco-post-quantum 1.13.0, so a fresh install brings the new core with it.

Sources

  1. NIST IR 8547, Transition to Post-Quantum Cryptography Standards, final, October 2026. csrc.nist.gov
  2. kxco-post-quantum on npm, version 1.13.0, published 29 October 2026. www.npmjs.com
  3. NIST Demo test server, session 783228: the 13 disposition files and the environment record, in the kxco-post-quantum repository. github.com
  4. kxco-post-quantum draft Security Policy, in the structure of NIST SP 800-140B. github.com
  5. kxco-pq-hsm on npm, versions 1.9.0 and 1.9.1, published 29 October 2026. www.npmjs.com
  6. kxco-pq-scan on npm, version 1.4.0, published 29 October 2026. www.npmjs.com
  7. kxco-pq on npm, version 3.0.1, published 29 October 2026. www.npmjs.com
  8. crypto-js on npm, version 4.2.0. www.npmjs.com
  9. KXCO, products and how they connect, read 29 October 2026. kxco.ai
  10. KXCO, architecture, read 29 October 2026. kxco.ai
  11. KXCO, post-quantum packages, read 29 October 2026. kxco.ai