@blamejs/blamejs-shop 0.1.11 → 0.1.12

package/CHANGELOG.md

@@ -8,6 +8,8 @@ upgrading across more than a few patches at a time.
 
 ## v0.1.x
 
+- v0.1.12 (2026-05-25) — **Card payments now finalize the order — the Stripe webhook is handled end to end.** A confirmed Stripe payment now advances the order from pending to paid. The container now serves the `POST /api/webhooks/stripe` route the edge worker forwards to: it re-verifies the event signature over the exact raw bytes, maps the event to the order's FSM transition, and is idempotent across Stripe's re-deliveries. Previously the edge verified the webhook but nothing consumed it on the container, so a paid PaymentIntent (card, Apple Pay, or Google Pay) left the order stuck in pending — no fulfillment, no paid status. Operators running checkout should upgrade and confirm their Stripe webhook points at `/api/webhooks/stripe`. **Added:** *Raw-body capture for payment webhooks* — A small middleware preserves the exact request bytes for the webhook path before the JSON body-parser runs, so signature verification (which is computed over the raw body) is reliable. It is scoped to the webhook routes and leaves every other request untouched. **Fixed:** *Stripe webhook completes the order* — `POST /api/webhooks/stripe` is now handled on the container: the event signature is re-verified against `STRIPE_WEBHOOK_SECRET` over the raw request body (a tampered or unsigned event is rejected with 400), then `payment_intent.succeeded` / `.canceled` / `charge.refunded` drive the order FSM (`mark_paid` / `cancel` / `refund`). Re-deliveries are idempotent — an event for an order already in the target state is acknowledged with 200 and skipped. A delivery for an unknown PaymentIntent is acknowledged without effect. This closes the gap where a confirmed payment never moved the order out of `pending`.
+
 - v0.1.11 (2026-05-25) — **Sign in with Apple.** Customers can now sign in with Apple, alongside passkeys and Google. A “Continue with Apple” button appears on the account login page once the operator wires the Apple credentials; the callback turns the verified Apple identity into a shop session, adopts the guest cart, and claims prior guest orders placed under the same verified email — the same way Google sign-in does. Apple's OAuth client secret is itself an ES256 JWT, which the shop mints from the team's Sign-in-with-Apple key. Sign in with Apple is off until the credentials are set, like every other integration. **Added:** *Sign in with Apple (OIDC)* — `GET /account/login/apple` starts the flow (sealed in-flight state cookie, PKCE, nonce); Apple posts the result back to `POST /account/auth/apple/callback` (response_mode=form_post). The callback verifies the state, exchanges the code, signs the customer in on `(provider=apple, subject)`, adopts the guest cart, and — when Apple reports the email as verified — claims prior guest orders under that email. The display name is captured from Apple's first-authorization `user` field (Apple sends it only once and never in the ID token). The button appears on `/account/login` only when the credentials are configured, and is listed on `/admin/integrations`. · *customers.mintAppleClientSecret* — Mints Apple's required ES256 client-secret JWT from a Services-ID `.p8` key (team id, key id, client id). This is the one signature the protocol forces to be classical ECDSA P-256 rather than the framework's post-quantum default — an external identity provider's wire format, not an application default. The secret is minted at boot with a 150-day life (inside Apple's six-month ceiling) and re-minted on each deploy. **Changed:** *Account login offers Apple when configured* — The login page shows Continue-with-Google and Continue-with-Apple buttons independently, each gated on its own credentials. Set `APPLE_TEAM_ID`, `APPLE_KEY_ID`, `APPLE_CLIENT_ID` (your Services ID), `APPLE_PRIVATE_KEY` (the `.p8` contents), and `SHOP_ORIGIN`, and add `<SHOP_ORIGIN>/account/auth/apple/callback` as a Return URL on the Services ID. Requires an Apple Developer Program membership. See the README “Optional integrations” section.
 
 - v0.1.10 (2026-05-25) — **Admin console — a review moderation screen.** Reviews join the admin console, completing the set of management screens. `/admin/reviews` is the moderation queue: filter by status (pending, published, rejected) and act on each submission inline — publish it, reject it with a reason, or take a published one back down. Reviews are short, so the queue shows each one in full (rating, title, body, verified-purchase flag) with its actions, no separate detail page. As with the other screens, every path content-negotiates: a bearer-token client gets the JSON API unchanged, a signed-in browser gets the HTML console. **Added:** *Review moderation screen* — `/admin/reviews` renders the review queue as inline cards (rating stars, title, body, verified-purchase flag, product, date) with status-filter chips, when opened in a signed-in browser; the same path serves the existing JSON list to a bearer-token client. Each card offers the actions that fit its status — a pending review can be published or rejected, a published one taken down, a rejected one published — with Reject taking a reason. Publish and reject post to their endpoints and redirect (PRG); a missing id is a no-op notice, never a 500. **Changed:** *Console nav gains Reviews; the reviews API content-negotiates* — The signed-in admin nav now includes Reviews — shown, like Returns, only when the reviews primitive is wired. The `/admin/reviews` list and the publish / reject endpoints serve the HTML console to a signed-in browser while continuing to serve the JSON API to a bearer-token client unchanged. A request without the bearer token is no longer answered with a 401 on the list path — a browser GET receives the sign-in form — matching the other console screens.

package/lib/storefront.js

@@ -34,6 +34,34 @@ function _b() {
   return bShop.framework;
 }
 
+// Payment-webhook signatures (Stripe's HMAC, PayPal's, …) are computed over
+// the EXACT raw request bytes, but the global JSON body-parser reparses and
+// discards them. This middleware buffers the raw body for the given POST
+// paths into `req.rawBody` BEFORE the body-parser runs, and pre-sets
+// `req.body` so the parser short-circuits (its `req.body !== undefined`
+// guard) instead of re-reading an already-drained stream. Mount it ahead of
+// `b.middleware.bodyParser()`; the webhook handlers read `req.rawBody`.
+function webhookRawBodyCapture(paths) {
+  var pathSet = {};
+  (paths || []).forEach(function (p) { pathSet[p] = true; });
+  // Compose the framework's raw body-parser (req.body ← a Buffer of the
+  // exact request bytes) instead of hand-reading the stream — it already
+  // honours the router's await/next contract and the byte-limit cap.
+  // Scoped to the webhook paths and mounted ahead of the global JSON parser:
+  // payment webhooks verify the signature over the raw body, which the JSON
+  // parser would reparse + discard. The JSON parser then skips these paths
+  // via its own `req.body !== undefined` guard.
+  var rawParser = _b().middleware.bodyParser.raw({
+    limit:        _b().constants.BYTES.mib(1),
+    contentTypes: ["application/json", "application/*"],
+  });
+  return function (req, res, next) {
+    var path = String(req.url || "").split("?")[0];
+    if ((req.method || "").toUpperCase() !== "POST" || !pathSet[path]) return next();
+    return rawParser(req, res, next);
+  };
+}
+
 // Re-use the strict renderer from the email primitive (same shape,
 // same XSS guard, same unknown / unused refusal).
 var _render = emailModule._render;
@@ -2898,6 +2926,36 @@ function mount(router, deps) {
         theme:          theme,
       }));
     });
+
+    // Stripe webhook — the order-completion path. A PaymentIntent succeeds
+    // asynchronously (the customer may close the tab before Stripe fires),
+    // so the order's pending→paid transition lands here, not on the return
+    // page. The body is verified over the RAW bytes (captured upstream by
+    // webhookRawBodyCapture into req.rawBody); handleStripeEvent re-verifies
+    // the signature, maps the event to an FSM transition, and dedupes
+    // Stripe's re-deliveries. A bad signature is 400; a handler error is
+    // 500 so Stripe retries; otherwise 200.
+    router.post("/api/webhooks/stripe", async function (req, res) {
+      // webhookRawBodyCapture set req.body to the exact bytes as a Buffer.
+      var raw = Buffer.isBuffer(req.body) ? req.body.toString("utf8")
+        : (typeof req.body === "string" ? req.body : "");
+      try {
+        var result = await deps.checkout.handleStripeEvent({ headers: req.headers || {}, rawBody: raw });
+        res.status(200);
+        res.setHeader && res.setHeader("content-type", "application/json; charset=utf-8");
+        var payload = JSON.stringify({ ok: true, handled: !!(result && result.handled) });
+        return res.end ? res.end(payload) : res.send(payload);
+      } catch (e) {
+        if (e && e.code === "WEBHOOK_INVALID") {
+          res.status(400);
+          return res.end ? res.end("invalid signature") : res.send("");
+        }
+        // A real failure (e.g. an illegal FSM transition) — 500 so Stripe
+        // retries the delivery rather than marking it permanently failed.
+        res.status(500);
+        return res.end ? res.end("handler error") : res.send("");
+      }
+    });
   }
 
   // ---- customer accounts (passkey-only) ------------------------------
@@ -4180,6 +4238,7 @@ function mount(router, deps) {
 
 module.exports = {
   mount:                 mount,
+  webhookRawBodyCapture: webhookRawBodyCapture,
   renderHome:            renderHome,
   renderSearch:          renderSearch,
   renderProduct:         renderProduct,

package/lib/vendor/MANIFEST.json

@@ -3,8 +3,8 @@
   "_about": "blamejs.shop vendors a single framework — blamejs — which itself bundles every server-side crypto/identity dependency. The transitive packages blamejs ships are surfaced in its own MANIFEST.json at lib/vendor/blamejs/lib/vendor/MANIFEST.json — Trivy / Grype rely on that nested data for CVE attribution.",
   "packages": {
     "blamejs": {
-      "version": "0.12.51",
-      "tag": "v0.12.51",
+      "version": "0.12.52",
+      "tag": "v0.12.52",
       "license": "Apache-2.0",
       "author": "blamejs contributors",
       "source": "https://github.com/blamejs/blamejs",

package/lib/vendor/blamejs/CHANGELOG.md

@@ -8,6 +8,8 @@ upgrading across more than a few patches at a time.
 
 ## v0.12.x
 
+- v0.12.52 (2026-05-25) — **`b.privacyPass` — Privacy Pass origin-side token verification (RFC 9577 / 9578).** Anonymous, publicly verifiable authorization: an origin issues a WWW-Authenticate: PrivateToken challenge and verifies a presented token cryptographically, without learning who the client is and without a callback to the issuer. b.privacyPass implements the publicly verifiable token type 0x0002 (Blind RSA, 2048-bit): the token's authenticator is an RSA Blind Signature (RFC 9474) checked as RSASSA-PSS (SHA-384, 48-byte salt) over token_input = token_type ‖ nonce ‖ challenge_digest ‖ token_key_id, using only the issuer's public key. The token is bound to that key (token_key_id) and, optionally, to the challenge it answers, so a token minted for another origin is refused. Blind RSA is the algorithm Privacy Pass defines on the wire — like the DNSSEC / DANE verifiers it validates an external protocol's signatures rather than introducing classical crypto as a framework default. Verified against the RFC 9578 §8.2 test vector. **Added:** *`b.privacyPass.verifyToken(opts)` / `parseToken` / `buildChallenge`* — `buildChallenge` builds a TokenChallenge (RFC 9577 §2.1) and the matching `WWW-Authenticate: PrivateToken challenge=…, token-key=…` header an origin returns to request a token, scoped to an issuer (and optionally an origin and a 32-byte redemption context). `parseToken` splits a token into its fields (type / nonce / challenge_digest / token_key_id / authenticator). `verifyToken` verifies a type 0x0002 (Blind RSA) token: it confirms the token's `token_key_id` is the SHA-256 of the supplied issuer public key, optionally that its `challenge_digest` matches `opts.challenge`, and that the authenticator is a valid RSASSA-PSS signature over the token input. Refuses unknown / privately verifiable token types (the VOPRF type 0x0001 needs the issuer secret and is an issuer-side operation), key-id and challenge mismatches, and tampered authenticators. Marked experimental while the issuance protocols see deployment.
+
 - v0.12.51 (2026-05-25) — **`b.network.dns.dane.matchCertificate` — DANE / TLSA certificate matching (RFC 6698 / 7671).** Pin a service's certificate through DNS instead of a public CA. matchCertificate checks a server certificate against a set of TLSA records: the selected data — the full certificate (selector 0) or its subjectPublicKeyInfo (selector 1) — is hashed per the matching type (exact / SHA-256 / SHA-512) and compared in constant time to the record's association data. For a DANE-EE (usage 3) record a match is self-authenticating — the TLSA pins the key, so no public-CA path is needed (the common SMTP-DANE case, RFC 7672); for the PKIX usages a match is reported as necessary-but-not-sufficient so the caller still runs PKIX. This is the payoff of the DNSSEC verifier: verify the TLSA RRset with b.network.dns.dnssec, then match the certificate. Verified against a live DNSSEC-signed TLSA record and the matching server certificate. **Added:** *`b.network.dns.dane.matchCertificate(opts)`* — Matches a leaf certificate (and optional `chain`) against a TLSA RRset (`{ usage, selector, matchingType, data }`). Selector 0 hashes the full certificate DER, selector 1 the subjectPublicKeyInfo; matching type 0 is an exact comparison, 1 SHA-256, 2 SHA-512 (SHA-1 and any other type are refused, not guessed). End-entity usages (PKIX-EE 1, DANE-EE 3) match the leaf; trust-anchor usages (PKIX-TA 0, DANE-TA 2) match the leaf or any supplied chain certificate. Returns `{ ok, matched, daneAuthenticated, trustAnchorMatch, pkixRequired, matchedCertIndex }` — `daneAuthenticated` is true only for a DANE-EE match (the key is pinned, no CA needed); `pkixRequired` flags the PKIX usages. Throws `dane/no-match` when nothing matches, and refuses unknown usage / selector / matching values and unparseable certificates. Verify the TLSA RRset with `b.network.dns.dnssec` first — an unauthenticated TLSA record proves nothing.
 
 - v0.12.50 (2026-05-25) — **`b.network.dns.dnssec.verifyChain` — validate a DNSSEC delegation chain to a pinned root anchor.** Completes local DNSSEC verification: validate a full delegation chain from the root down to a zone against a pinned trust anchor (RFC 4035 §5), instead of trusting any single resolver. For each link, the zone's DNSKEY RRset must be self-signed by one of its keys, and that key must be vouched for either by a pinned anchor (at the root) or by a DS record served + signed by the already-trusted parent — so trust flows root → TLD → zone with no gap. The IANA root KSKs (KSK-2017 tag 20326, KSK-2024 tag 38696) ship as the default anchors; override with opts.trustAnchors for a private root. verifyChain returns the leaf zone's trusted DNSKEY set, which you then hand to verifyRrset / verifyDenial for the actual answer. Composes verifyRrset + verifyDs + the key tag; verified end-to-end against a live root→org chain. **Added:** *`b.network.dns.dnssec.verifyChain(opts)`* — Walks an ordered, root-first list of `links` ({ zone, dnskeys, dnskeyRrsig, dsRdatas?, dsRrsig? }). At each link it verifies the DNSKEY RRset's self-signature (composing `verifyRrset`), then establishes trust in the signing key: at the root by matching a pinned anchor's DS digest (`verifyDs`), at every delegation by verifying the parent-served DS RRset's signature with the already-trusted parent key and confirming the signing KSK matches one of those DS records. Returns `{ ok, zone, keys, path }` with the leaf zone's trusted DNSKEY set. Refuses a root key that matches no anchor (`dnssec/chain-anchor-mismatch`), a KSK that matches no parent DS (`dnssec/chain-ds-mismatch`), and a missing parent key (`dnssec/chain-no-parent-key`). The default `DEFAULT_ROOT_ANCHORS` are the published IANA root KSK DS records; `opts.trustAnchors` overrides them for a private or test root.

package/lib/vendor/blamejs/README.md

@@ -89,6 +89,7 @@ The framework bundles the surface a typical Node app reaches for. Every primitiv
 - **Financial / Open Banking** — FAPI 2.0 Final composite posture (PAR + PKCE-S256 + DPoP-or-mTLS + RFC 9207); runtime enforcement helpers `b.fapi2.assertCallback` (refuses missing iss + bare-param under message-signing) and `b.fapi2.assertAuthzRequest` (refuses non-JAR); CFPB §1033 / FDX 6.0 consumer-financial-data-sharing wrapper (`b.fdx`)
 - **Data-subject coordination** — cross-table export / rectify / erase / restrict / objection (`b.subject`, `b.subject.eraseHard`); subject-level legal-hold registry consulted by erase + retention paths (FRCP Rule 26/37(e), GDPR Art 17(3)(e), SEC Rule 17a-4, HIPAA §164.530(j)(2)) (`b.legalHold`)
 - **Account safety** — adaptive bot-challenge staircase (`b.authBotChallenge`); session-to-device-posture binding with fail-closed verify (`b.sessionDeviceBinding`)
+- **Anonymous authorization** — Privacy Pass origin side (RFC 9577/9578 — `b.privacyPass`): issue a `WWW-Authenticate: PrivateToken` challenge and verify a presented Blind-RSA (type 0x0002) token against the issuer public key, with no issuer callback and no client identity
 ### Crypto
 
 - **At-rest envelope** — envelope-versioned PQC (ML-KEM-1024 + P-384 hybrid, XChaCha20-Poly1305, SHAKE256); vault sealing (`b.crypto`, `b.vault`)

package/lib/vendor/blamejs/api-snapshot.json

@@ -1,7 +1,7 @@
 {
   "version": 1,
-  "frameworkVersion": "0.12.51",
-  "createdAt": "2026-05-25T14:53:56.538Z",
+  "frameworkVersion": "0.12.52",
+  "createdAt": "2026-05-25T16:02:59.536Z",
   "exports": {
     "a2a": {
       "type": "object",
@@ -44979,6 +44979,31 @@
         }
       }
     },
+    "privacyPass": {
+      "type": "object",
+      "members": {
+        "PrivacyPassError": {
+          "type": "function",
+          "arity": 4
+        },
+        "TOKEN_TYPE_BLIND_RSA": {
+          "type": "primitive",
+          "valueType": "number"
+        },
+        "buildChallenge": {
+          "type": "function",
+          "arity": 1
+        },
+        "parseToken": {
+          "type": "function",
+          "arity": 1
+        },
+        "verifyToken": {
+          "type": "function",
+          "arity": 1
+        }
+      }
+    },
     "problemDetails": {
       "type": "object",
       "members": {

package/lib/vendor/blamejs/index.js

@@ -394,6 +394,7 @@ var webPush = require("./lib/web-push-vapid");
 var fedcm = require("./lib/fedcm");
 var dbsc = require("./lib/dbsc");
 var importmapIntegrity = require("./lib/importmap-integrity");
+var privacyPass = require("./lib/privacy-pass");
 var standardWebhooks = require("./lib/standard-webhooks");
 var lro = require("./lib/lro");
 var jsonApi = require("./lib/jsonapi");
@@ -409,6 +410,7 @@ module.exports = {
   fedcm:            fedcm,
   dbsc:             dbsc,
   importmapIntegrity: importmapIntegrity,
+  privacyPass:      privacyPass,
   standardWebhooks: standardWebhooks,
   lro:              lro,
   jsonApi:          jsonApi,

package/lib/vendor/blamejs/lib/privacy-pass.js

@@ -0,0 +1,267 @@
+"use strict";
+/**
+ * @module b.privacyPass
+ * @nav    Identity
+ * @title  Privacy Pass
+ *
+ * @intro
+ *   Origin / relying-party side of Privacy Pass (RFC 9577 HTTP
+ *   authentication scheme, RFC 9578 issuance protocols) — issue a token
+ *   challenge and verify a presented token without learning who the
+ *   client is. An origin asks for a token with a
+ *   <code>WWW-Authenticate: PrivateToken</code> challenge; the client
+ *   obtains a token from an issuer and presents it; the origin verifies
+ *   it cryptographically.
+ *
+ *   This implements the publicly verifiable token type
+ *   <strong>0x0002 (Blind RSA, 2048-bit)</strong>: the token's
+ *   authenticator is an RSA Blind Signature (RFC 9474) that any party
+ *   holding the issuer's public key can verify with RSASSA-PSS — so the
+ *   origin verifies tokens itself, with no issuer secret and no callback.
+ *   The privately verifiable VOPRF type (0x0001) requires the issuer's
+ *   secret key and is an issuer-side operation, not implemented here.
+ *
+ *   Blind RSA is the algorithm Privacy Pass defines on the wire; like
+ *   the framework's DNSSEC / DANE verifiers it validates an external
+ *   protocol's signatures (RSASSA-PSS, SHA-384) rather than introducing
+ *   classical crypto as a framework default.
+ *
+ * @card
+ *   Privacy Pass origin side (RFC 9577 / 9578). Issue a
+ *   <code>WWW-Authenticate: PrivateToken</code> challenge and verify a
+ *   presented Blind-RSA (type 0x0002) token against the issuer public
+ *   key — anonymous, publicly verifiable authorization with no issuer
+ *   callback.
+ */
+
+var nodeCrypto = require("node:crypto");
+var bCrypto = require("./crypto");
+var validateOpts = require("./validate-opts");
+var { defineClass } = require("./framework-error");
+
+var PrivacyPassError = defineClass("PrivacyPassError", { alwaysPermanent: true });
+
+var TOKEN_TYPE_BLIND_RSA = 0x0002;
+// RFC 9578 §5.3 token type 0x0002: RSABSSA-SHA384-PSS, salt length 48.
+var PSS_HASH = "sha384";
+var PSS_SALT_LEN = 48;                                        // allow:raw-byte-literal — RFC 9578 §5.3 PSS salt length (= SHA-384 digest size)
+// Fixed-size token fields (RFC 9577 §2.2): type(2) nonce(32)
+// challenge_digest(32) token_key_id(32), then the authenticator.
+var TOKEN_PREFIX_LEN = 98;                                    // allow:raw-byte-literal — 2 + 32 + 32 + 32 (token_input length)
+
+// RFC 9577 §2.1 sends the challenge / token-key auth-params as base64url
+// WITH padding; Node's "base64url" output is unpadded, so pad to a
+// multiple of 4 so strict clients / proxies accept the header.
+function _b64urlPadded(buf) {
+  var s = Buffer.from(buf).toString("base64url");
+  while (s.length % 4 !== 0) s += "=";                        // allow:raw-byte-literal — base64 quantum is 4 chars
+  return s;
+}
+
+function _bytes(x, what) {
+  if (Buffer.isBuffer(x)) return x;
+  if (x instanceof Uint8Array) return Buffer.from(x);
+  if (typeof x === "string") return Buffer.from(x, "base64");
+  throw new PrivacyPassError("privacy-pass/bad-bytes", "privacyPass: " + what + " must be a Buffer / Uint8Array / base64 string");
+}
+
+// Import the issuer public key and capture the SubjectPublicKeyInfo
+// bytes used to derive token_key_id. When the caller supplies the
+// published SPKI DER directly, hash THOSE bytes — re-exporting an
+// rsa-pss KeyObject can re-encode the AlgorithmIdentifier and change the
+// digest. token_key_id is SHA-256 of the issuer's distributed key
+// (RFC 9577 §2.2), which is the SPKI as published.
+function _importIssuerKey(k) {
+  if (k && typeof k === "object" && typeof k.export === "function" && k.type === "public") {
+    return { key: k, spki: k.export({ format: "der", type: "spki" }) };
+  }
+  try {
+    if (Buffer.isBuffer(k) || k instanceof Uint8Array) {
+      var der = Buffer.from(k);
+      return { key: nodeCrypto.createPublicKey({ key: der, format: "der", type: "spki" }), spki: der };
+    }
+    // A "PUBLIC KEY" PEM body IS the SubjectPublicKeyInfo DER — decode it
+    // directly so token_key_id is SHA-256 of the issuer's exact bytes,
+    // not a re-encoding (Node can re-emit rsa-pss AlgorithmIdentifier
+    // parameters differently on export).
+    if (typeof k === "string" && /-----BEGIN PUBLIC KEY-----/.test(k)) {
+      var body = k.replace(/-----BEGIN PUBLIC KEY-----/, "").replace(/-----END PUBLIC KEY-----/, "").replace(/\s+/g, "");
+      var pemDer = Buffer.from(body, "base64");
+      return { key: nodeCrypto.createPublicKey(k), spki: pemDer };
+    }
+    var key = nodeCrypto.createPublicKey(k);                  // other key spec (best-effort SPKI export)
+    return { key: key, spki: key.export({ format: "der", type: "spki" }) };
+  } catch (e) {
+    throw new PrivacyPassError("privacy-pass/bad-key", "privacyPass: could not import issuerPublicKey: " + ((e && e.message) || e));
+  }
+}
+
+/**
+ * @primitive b.privacyPass.parseToken
+ * @signature b.privacyPass.parseToken(token)
+ * @since     0.12.52
+ * @status    experimental
+ * @related   b.privacyPass.verifyToken, b.privacyPass.buildChallenge
+ *
+ * Parse a Privacy Pass token (RFC 9577 §2.2) into its fields: the
+ * <code>tokenType</code>, the client <code>nonce</code>, the
+ * <code>challengeDigest</code> (SHA-256 of the TokenChallenge the token
+ * answers), the <code>tokenKeyId</code> (SHA-256 of the issuer public
+ * key), and the <code>authenticator</code>. Structural only — call
+ * <code>verifyToken</code> to check the signature.
+ *
+ * @example
+ *   var t = b.privacyPass.parseToken(tokenBytes);
+ *   // → { tokenType: 2, nonce, challengeDigest, tokenKeyId, authenticator }
+ */
+function parseToken(token) {
+  var b = _bytes(token, "token");
+  if (b.length < TOKEN_PREFIX_LEN + 1) throw new PrivacyPassError("privacy-pass/bad-token", "privacyPass.parseToken: token too short");
+  return {
+    tokenType:       b.readUInt16BE(0),
+    nonce:           b.slice(2, 34),
+    challengeDigest: b.slice(34, 66),
+    tokenKeyId:      b.slice(66, 98),
+    authenticator:   b.slice(98),
+    tokenInput:      b.slice(0, TOKEN_PREFIX_LEN),
+  };
+}
+
+/**
+ * @primitive b.privacyPass.verifyToken
+ * @signature b.privacyPass.verifyToken(opts)
+ * @since     0.12.52
+ * @status    experimental
+ * @compliance soc2
+ * @related   b.privacyPass.buildChallenge, b.privacyPass.parseToken
+ *
+ * Verify a publicly verifiable Privacy Pass token (type 0x0002, Blind
+ * RSA — RFC 9578 §8.2). The authenticator is checked as an RSASSA-PSS
+ * (SHA-384, MGF1-SHA-384, 48-byte salt) signature over
+ * <code>token_input = token_type ‖ nonce ‖ challenge_digest ‖
+ * token_key_id</code> using the issuer's public key. The token is bound
+ * to that key — its <code>token_key_id</code> must equal the SHA-256 of
+ * the supplied key's SubjectPublicKeyInfo — and, when
+ * <code>opts.challenge</code> is given, to that challenge (its SHA-256
+ * must equal the token's <code>challenge_digest</code>), so a token
+ * minted for a different origin's challenge is refused.
+ *
+ * @opts
+ *   {
+ *     token:            Buffer|base64,   // the presented token
+ *     issuerPublicKey:  KeyObject|Buffer(SPKI DER)|PEM,
+ *     challenge?:       Buffer|base64,   // the TokenChallenge this token must answer
+ *   }
+ *
+ * @example
+ *   var r = b.privacyPass.verifyToken({ token: tok, issuerPublicKey: issuerSpki });
+ *   // → { ok: true, tokenType: 2, nonce, challengeDigest, tokenKeyId }
+ */
+function verifyToken(opts) {
+  validateOpts.requireObject(opts, "privacyPass.verifyToken", PrivacyPassError);
+  validateOpts(opts, ["token", "issuerPublicKey", "challenge"], "privacyPass.verifyToken");
+  if (opts.issuerPublicKey === undefined || opts.issuerPublicKey === null) throw new PrivacyPassError("privacy-pass/bad-arg", "privacyPass.verifyToken: opts.issuerPublicKey is required");
+
+  var parsed = parseToken(opts.token);
+  if (parsed.tokenType !== TOKEN_TYPE_BLIND_RSA) {
+    throw new PrivacyPassError("privacy-pass/unsupported-token-type", "privacyPass.verifyToken: only token type 0x0002 (Blind RSA) is verifiable by the origin; got 0x" + parsed.tokenType.toString(16).padStart(4, "0"));  // allow:raw-byte-literal — base-16 radix + 4-hex-digit pad, not a size
+  }
+
+  var imported = _importIssuerKey(opts.issuerPublicKey);
+  var key = imported.key;
+  if (key.asymmetricKeyType !== "rsa" && key.asymmetricKeyType !== "rsa-pss") {
+    throw new PrivacyPassError("privacy-pass/bad-key", "privacyPass.verifyToken: issuerPublicKey must be an RSA key for token type 0x0002");
+  }
+
+  // Bind the token to the issuer key: token_key_id = SHA-256(SPKI).
+  var keyId = nodeCrypto.createHash("sha256").update(imported.spki).digest();
+  if (!bCrypto.timingSafeEqual(keyId, parsed.tokenKeyId)) {
+    throw new PrivacyPassError("privacy-pass/key-id-mismatch", "privacyPass.verifyToken: token_key_id does not match the issuer public key");
+  }
+
+  // Bind the token to the challenge, when supplied.
+  if (opts.challenge !== undefined && opts.challenge !== null) {
+    var cd = nodeCrypto.createHash("sha256").update(_bytes(opts.challenge, "challenge")).digest();
+    if (!bCrypto.timingSafeEqual(cd, parsed.challengeDigest)) {
+      throw new PrivacyPassError("privacy-pass/challenge-mismatch", "privacyPass.verifyToken: challenge_digest does not match opts.challenge");
+    }
+  }
+
+  var ok;
+  try {
+    ok = nodeCrypto.verify(PSS_HASH, parsed.tokenInput, { key: key, padding: nodeCrypto.constants.RSA_PKCS1_PSS_PADDING, saltLength: PSS_SALT_LEN }, parsed.authenticator);
+  } catch (e) {
+    throw new PrivacyPassError("privacy-pass/verify-threw", "privacyPass.verifyToken: signature verification threw: " + ((e && e.message) || e));
+  }
+  if (!ok) throw new PrivacyPassError("privacy-pass/bad-authenticator", "privacyPass.verifyToken: token authenticator did not verify");
+  return { ok: true, tokenType: parsed.tokenType, nonce: parsed.nonce, challengeDigest: parsed.challengeDigest, tokenKeyId: parsed.tokenKeyId };
+}
+
+/**
+ * @primitive b.privacyPass.buildChallenge
+ * @signature b.privacyPass.buildChallenge(opts)
+ * @since     0.12.52
+ * @status    experimental
+ * @related   b.privacyPass.verifyToken
+ *
+ * Build a TokenChallenge (RFC 9577 §2.1) and the matching
+ * <code>WWW-Authenticate: PrivateToken</code> header value an origin
+ * returns to ask a client for a token. The challenge binds the token to
+ * this issuer (and optionally this origin and a redemption context);
+ * its SHA-256 is the <code>challenge_digest</code> that
+ * <code>verifyToken</code> checks.
+ *
+ * @opts
+ *   {
+ *     issuerName:        string,   // the token issuer's name
+ *     tokenType?:        number,   // default 0x0002 (Blind RSA)
+ *     originInfo?:       string,   // origin name(s) the token is scoped to (default: any)
+ *     redemptionContext?: Buffer,  // 0 or 32 bytes (default: empty)
+ *     tokenKey?:         Buffer|KeyObject,  // issuer SPKI, included as token-key= when given
+ *   }
+ *
+ * @example
+ *   var c = b.privacyPass.buildChallenge({ issuerName: "issuer.example", originInfo: "origin.example" });
+ *   res.setHeader("WWW-Authenticate", c.wwwAuthenticate);
+ */
+function buildChallenge(opts) {
+  validateOpts.requireObject(opts, "privacyPass.buildChallenge", PrivacyPassError);
+  validateOpts(opts, ["issuerName", "tokenType", "originInfo", "redemptionContext", "tokenKey"], "privacyPass.buildChallenge");
+  if (typeof opts.issuerName !== "string" || opts.issuerName === "") throw new PrivacyPassError("privacy-pass/bad-arg", "privacyPass.buildChallenge: opts.issuerName is required");
+  var tokenType = opts.tokenType === undefined ? TOKEN_TYPE_BLIND_RSA : opts.tokenType;
+  if (typeof tokenType !== "number" || !Number.isInteger(tokenType) || tokenType < 0 || tokenType > 0xffff) throw new PrivacyPassError("privacy-pass/bad-arg", "privacyPass.buildChallenge: tokenType must be a uint16");
+
+  var issuer = Buffer.from(opts.issuerName, "utf8");
+  if (issuer.length > 0xffff) throw new PrivacyPassError("privacy-pass/bad-arg", "privacyPass.buildChallenge: issuerName too long");
+  var origin = Buffer.alloc(0);
+  if (opts.originInfo !== undefined && opts.originInfo !== null) {
+    if (typeof opts.originInfo !== "string") throw new PrivacyPassError("privacy-pass/bad-arg", "privacyPass.buildChallenge: originInfo must be a string");
+    origin = Buffer.from(opts.originInfo, "utf8");
+    if (origin.length > 0xffff) throw new PrivacyPassError("privacy-pass/bad-arg", "privacyPass.buildChallenge: originInfo too long");
+  }
+  var rc = opts.redemptionContext !== undefined && opts.redemptionContext !== null ? _bytes(opts.redemptionContext, "redemptionContext") : Buffer.alloc(0);
+  if (rc.length !== 0 && rc.length !== 32) throw new PrivacyPassError("privacy-pass/bad-arg", "privacyPass.buildChallenge: redemptionContext must be empty or 32 bytes");  // allow:raw-byte-literal — RFC 9577 redemption_context is 0 or 32 bytes
+
+  var u16 = function (n) { return Buffer.from([(n >> 8) & 0xff, n & 0xff]); };
+  var challenge = Buffer.concat([
+    u16(tokenType),
+    u16(issuer.length), issuer,
+    Buffer.from([rc.length]), rc,
+    u16(origin.length), origin,
+  ]);
+
+  var parts = ['PrivateToken challenge="' + _b64urlPadded(challenge) + '"'];
+  if (opts.tokenKey !== undefined && opts.tokenKey !== null) {
+    var spki = (opts.tokenKey && typeof opts.tokenKey.export === "function") ? opts.tokenKey.export({ format: "der", type: "spki" }) : _bytes(opts.tokenKey, "tokenKey");
+    parts.push('token-key="' + _b64urlPadded(spki) + '"');
+  }
+  return { challenge: challenge, wwwAuthenticate: parts.join(", ") };
+}
+
+module.exports = {
+  parseToken:     parseToken,
+  verifyToken:    verifyToken,
+  buildChallenge: buildChallenge,
+  TOKEN_TYPE_BLIND_RSA: TOKEN_TYPE_BLIND_RSA,
+  PrivacyPassError: PrivacyPassError,
+};

package/lib/vendor/blamejs/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@blamejs/core",
-  "version": "0.12.51",
+  "version": "0.12.52",
   "description": "The Node framework that owns its stack.",
   "license": "Apache-2.0",
   "author": "blamejs contributors",

package/lib/vendor/blamejs/release-notes/v0.12.52.json

@@ -0,0 +1,18 @@
+{
+  "$schema": "../scripts/release-notes-schema.json",
+  "version": "0.12.52",
+  "date": "2026-05-25",
+  "headline": "`b.privacyPass` — Privacy Pass origin-side token verification (RFC 9577 / 9578)",
+  "summary": "Anonymous, publicly verifiable authorization: an origin issues a WWW-Authenticate: PrivateToken challenge and verifies a presented token cryptographically, without learning who the client is and without a callback to the issuer. b.privacyPass implements the publicly verifiable token type 0x0002 (Blind RSA, 2048-bit): the token's authenticator is an RSA Blind Signature (RFC 9474) checked as RSASSA-PSS (SHA-384, 48-byte salt) over token_input = token_type ‖ nonce ‖ challenge_digest ‖ token_key_id, using only the issuer's public key. The token is bound to that key (token_key_id) and, optionally, to the challenge it answers, so a token minted for another origin is refused. Blind RSA is the algorithm Privacy Pass defines on the wire — like the DNSSEC / DANE verifiers it validates an external protocol's signatures rather than introducing classical crypto as a framework default. Verified against the RFC 9578 §8.2 test vector.",
+  "sections": [
+    {
+      "heading": "Added",
+      "items": [
+        {
+          "title": "`b.privacyPass.verifyToken(opts)` / `parseToken` / `buildChallenge`",
+          "body": "`buildChallenge` builds a TokenChallenge (RFC 9577 §2.1) and the matching `WWW-Authenticate: PrivateToken challenge=…, token-key=…` header an origin returns to request a token, scoped to an issuer (and optionally an origin and a 32-byte redemption context). `parseToken` splits a token into its fields (type / nonce / challenge_digest / token_key_id / authenticator). `verifyToken` verifies a type 0x0002 (Blind RSA) token: it confirms the token's `token_key_id` is the SHA-256 of the supplied issuer public key, optionally that its `challenge_digest` matches `opts.challenge`, and that the authenticator is a valid RSASSA-PSS signature over the token input. Refuses unknown / privately verifiable token types (the VOPRF type 0x0001 needs the issuer secret and is an issuer-side operation), key-id and challenge mismatches, and tampered authenticators. Marked experimental while the issuance protocols see deployment."
+        }
+      ]
+    }
+  ]
+}

package/lib/vendor/blamejs/test/layer-0-primitives/codebase-patterns.test.js

@@ -2271,9 +2271,10 @@ async function testNoDuplicateCodeBlocks() {
         "lib/mdoc.js:_bytes",
         "lib/network-dnssec.js:_bytes",
         "lib/network-dane.js:_bytes",
+        "lib/privacy-pass.js:_bytes",
         "lib/tsa.js:_bytes",
       ],
-      reason: "v0.12.48 / v0.12.51 — Buffer-coercion guard (`if (Buffer.isBuffer(x)) return x; if (x instanceof Uint8Array) return Buffer.from(x); throw <Error>`) repeats across byte-string-consuming primitives. Each throws a MODULE-LOCAL typed error code (cose/bad-cose-key, mdoc/bad-input, dnssec/bad-bytes, dane/bad-bytes, tsa/bad-input) naming the local argument; network-dane additionally coerces a hex string. The duplicated three-line shape is the symptom, the cause is that JS can't throw a caller-namespaced ErrorClass without the local closure. Same documented exception as the v0.12.7 require-non-empty-string cluster — the typed-error CODE is the divergence the dup detector can't see.",
+      reason: "v0.12.48 / v0.12.51 / v0.12.52 — Buffer-coercion guard (`if (Buffer.isBuffer(x)) return x; if (x instanceof Uint8Array) return Buffer.from(x); throw <Error>`) repeats across byte-string-consuming primitives. Each throws a MODULE-LOCAL typed error code (cose/bad-cose-key, mdoc/bad-input, dnssec/bad-bytes, dane/bad-bytes, tsa/bad-input) naming the local argument; network-dane additionally coerces a hex string. The duplicated three-line shape is the symptom, the cause is that JS can't throw a caller-namespaced ErrorClass without the local closure. Same documented exception as the v0.12.7 require-non-empty-string cluster — the typed-error CODE is the divergence the dup detector can't see.",
     },
     {
       mode:  "family-subset",

package/lib/vendor/blamejs/test/layer-0-primitives/privacy-pass.test.js

@@ -0,0 +1,120 @@
+"use strict";
+/**
+ * Layer 0 — b.privacyPass (Privacy Pass origin side, RFC 9577 / 9578).
+ * The oracle is the published RFC 9578 §8.2 test vector for token type
+ * 0x0002 (Blind RSA): the issuer public key, the TokenChallenge, and the
+ * issued token. A wrong token_input layout or PSS parameter would fail
+ * the real RSASSA-PSS verification, and the build-then-digest round trip
+ * reproduces the vector's challenge_digest byte-for-byte.
+ */
+
+var b = require("../../index");
+var helpers = require("../helpers");
+var check = helpers.check;
+var crypto = require("node:crypto");
+
+// RFC 9578 §8.2, test vector 1 (token type 0x0002, Blind RSA 2048).
+var PKI_SPKI_HEX = "30820152303d06092a864886f70d01010a3030a00d300b0609608648016503040202a11a301806092a864886f70d010108300b0609608648016503040202a2030201300382010f003082010a0282010100cb1aed6b6a95f5b1ce013a4cfcab25b94b2e64a23034e4250a7eab43c0df3a8c12993af12b111908d4b471bec31d4b6c9ad9cdda90612a2ee903523e6de5a224d6b02f09e5c374d0cfe01d8f529c500a78a2f67908fa682b5a2b430c81eaf1af72d7b5e794fc98a3139276879757ce453b526ef9bf6ceb99979b8423b90f4461a22af37aab0cf5733f7597abe44d31c732db68a181c6cbbe607d8c0e52e0655fd9996dc584eca0be87afbcd78a337d17b1dba9e828bbd81e291317144e7ff89f55619709b096cbb9ea474cead264c2073fe49740c01f00e109106066983d21e5f83f086e2e823c879cd43cef700d2a352a9babd612d03cad02db134b7e225a5f0203010001";
+var TOKEN_CHALLENGE_HEX = "0002000e6973737565722e6578616d706c65208e7acc900e393381e8810b7c9e4a68b5163f1f880ab6688a6ffe780923609e88000e6f726967696e2e6578616d706c65";
+var TOKEN_HEX = "0002aa72019d1f951df197021ce63876fe8b0a02dc1c31a12b0a2dd1508d07827f055969f643b4cfda5196d4aa86aeb5368834f4f06de46950ed435b3b81bd036d44ca572f8982a9ca248a3056186322d93ca147266121ddeb5632c07f1f71cd2708bc6a21b533d07294b5e900faf5537dd3eb33cee4e08c9670d1e5358fd184b0e00c637174f5206b14c7bb0e724ebf6b56271e5aa2ed94c051c4a433d302b23bc52460810d489fb050f9de5c868c6c1b06e3849fd087629f704cc724bc0d0984d5c339686fcdd75f9a9cdd25f37f855f6f4c584d84f716864f546b696d620c5bd41a811498de84ff9740ba3003ba2422d26b91eb745c084758974642a42078201543246ddb58030ea8e722376aa82484dca9610a8fb7e018e396165462e17a03e40ea7e128c090a911ecc708066cb201833010c1ebd4e910fc8e27a1be467f78671836a508257123a45e4e0ae2180a434bd1037713466347a8ebe46439d3da1970";
+
+function spki() { return Buffer.from(PKI_SPKI_HEX, "hex"); }
+function token() { return Buffer.from(TOKEN_HEX, "hex"); }
+function challenge() { return Buffer.from(TOKEN_CHALLENGE_HEX, "hex"); }
+function code(fn) { try { fn(); return "NO-THROW"; } catch (e) { return e.code; } }
+
+function testSurface() {
+  check("b.privacyPass.verifyToken is a function", typeof b.privacyPass.verifyToken === "function");
+  check("b.privacyPass.parseToken is a function", typeof b.privacyPass.parseToken === "function");
+  check("b.privacyPass.buildChallenge is a function", typeof b.privacyPass.buildChallenge === "function");
+  check("b.privacyPass.TOKEN_TYPE_BLIND_RSA is 0x0002", b.privacyPass.TOKEN_TYPE_BLIND_RSA === 0x0002);
+  check("b.privacyPass.PrivacyPassError is the typed error class", typeof b.privacyPass.PrivacyPassError === "function" && code(function () { b.privacyPass.parseToken(Buffer.alloc(2)); }) === "privacy-pass/bad-token");
+  var threw = null; try { b.privacyPass.parseToken(Buffer.alloc(2)); } catch (e) { threw = e; }
+  check("PrivacyPassError instances are thrown", threw instanceof b.privacyPass.PrivacyPassError);
+}
+
+function testParse() {
+  var t = b.privacyPass.parseToken(token());
+  check("parseToken: token type 0x0002", t.tokenType === 0x0002);
+  check("parseToken: 32-byte nonce / digest / key-id", t.nonce.length === 32 && t.challengeDigest.length === 32 && t.tokenKeyId.length === 32);
+  check("parseToken: 256-byte authenticator (RSA-2048)", t.authenticator.length === 256);
+  // The embedded token_key_id is SHA-256 of the issuer SPKI.
+  var keyId = crypto.createHash("sha256").update(spki()).digest();
+  check("parseToken: token_key_id == SHA-256(issuer SPKI)", Buffer.compare(keyId, t.tokenKeyId) === 0);
+}
+
+function testRealVector() {
+  var out = b.privacyPass.verifyToken({ token: token(), issuerPublicKey: spki() });
+  check("verifyToken: real RFC 9578 §8.2 Blind RSA token verifies", out.ok && out.tokenType === 0x0002);
+  // Bound to the challenge it answers.
+  var out2 = b.privacyPass.verifyToken({ token: token(), issuerPublicKey: spki(), challenge: challenge() });
+  check("verifyToken: verifies when bound to the matching challenge", out2.ok === true);
+}
+
+function testBuildChallengeRoundTrip() {
+  // Rebuilding the vector's TokenChallenge reproduces it byte-for-byte,
+  // and its SHA-256 is the challenge_digest embedded in the token.
+  var rc = challenge().slice(19, 51); // the 32-byte redemption_context (after the 1-byte length at offset 18)
+  var c = b.privacyPass.buildChallenge({ issuerName: "issuer.example", originInfo: "origin.example", redemptionContext: rc });
+  check("buildChallenge: reproduces the RFC TokenChallenge bytes", Buffer.compare(c.challenge, challenge()) === 0);
+  var digest = crypto.createHash("sha256").update(c.challenge).digest();
+  var t = b.privacyPass.parseToken(token());
+  check("buildChallenge: SHA-256(challenge) == token challenge_digest", Buffer.compare(digest, t.challengeDigest) === 0);
+  check("buildChallenge: emits a PrivateToken WWW-Authenticate header", /^PrivateToken challenge="/.test(c.wwwAuthenticate));
+  // RFC 9577 §2.1: auth-param values are padded base64url.
+  var cv = c.wwwAuthenticate.match(/challenge="([^"]+)"/)[1];
+  check("buildChallenge: challenge value is base64url with padding (len % 4 === 0)", cv.length % 4 === 0 && !/[+/]/.test(cv));
+  var ck = b.privacyPass.buildChallenge({ issuerName: "issuer.example", tokenKey: spki() });
+  check("buildChallenge: token-key value is padded base64url", /token-key="([^"]+)"/.test(ck.wwwAuthenticate) && ck.wwwAuthenticate.match(/token-key="([^"]+)"/)[1].length % 4 === 0);
+}
+
+function testPemKeyId() {
+  // A PEM-encoded issuer key must derive the same token_key_id as the raw
+  // SPKI bytes (Node can re-encode an rsa-pss AlgorithmIdentifier on
+  // export, so the PEM body bytes — not a re-export — must be hashed).
+  var pem = "-----BEGIN PUBLIC KEY-----\n" + spki().toString("base64").replace(/(.{64})/g, "$1\n").replace(/\n$/, "") + "\n-----END PUBLIC KEY-----\n";
+  var out = b.privacyPass.verifyToken({ token: token(), issuerPublicKey: pem });
+  check("verifyToken: real token verifies with a PEM issuer key", out.ok === true);
+}
+
+function testRefusals() {
+  // Tampered authenticator fails.
+  check("verifyToken: tampered authenticator refused", code(function () {
+    var bad = token(); bad[bad.length - 1] ^= 0xff;
+    b.privacyPass.verifyToken({ token: bad, issuerPublicKey: spki() });
+  }) === "privacy-pass/bad-authenticator");
+  // Wrong issuer key → token_key_id mismatch (caught before signature).
+  check("verifyToken: wrong issuer key refused (key-id mismatch)", code(function () {
+    var otherKey = crypto.generateKeyPairSync("rsa", { modulusLength: 2048 }).publicKey.export({ format: "der", type: "spki" });
+    b.privacyPass.verifyToken({ token: token(), issuerPublicKey: otherKey });
+  }) === "privacy-pass/key-id-mismatch");
+  // Wrong challenge → challenge_digest mismatch.
+  check("verifyToken: mismatched challenge refused", code(function () {
+    b.privacyPass.verifyToken({ token: token(), issuerPublicKey: spki(), challenge: Buffer.from("not the challenge") });
+  }) === "privacy-pass/challenge-mismatch");
+  // Privately verifiable VOPRF (0x0001) is not an origin-verify operation.
+  check("verifyToken: token type 0x0001 (VOPRF) refused", code(function () {
+    var t = token(); t.writeUInt16BE(0x0001, 0);
+    b.privacyPass.verifyToken({ token: t, issuerPublicKey: spki() });
+  }) === "privacy-pass/unsupported-token-type");
+  // Truncated token refused.
+  check("parseToken: short token refused", code(function () { b.privacyPass.parseToken(Buffer.alloc(40)); }) === "privacy-pass/bad-token");
+}
+
+async function run() {
+  testSurface();
+  testParse();
+  testRealVector();
+  testBuildChallengeRoundTrip();
+  testPemKeyId();
+  testRefusals();
+}
+
+module.exports = { run: run };
+
+if (require.main === module) {
+  run().then(
+    function () { console.log("[privacy-pass] OK — " + helpers.getChecks() + " checks passed"); },
+    function (e) { console.error("FAIL:", e && e.stack || e); process.exit(1); }
+  );
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@blamejs/blamejs-shop",
-  "version": "0.1.11",
+  "version": "0.1.12",
   "description": "Open-source framework built on blamejs. Vendored stack, zero npm runtime deps, PQC-first crypto, security-on by default.",
   "main": "lib/index.js",
   "scripts": {