@onesub/server 0.19.0 → 0.21.0

package/README.md

@@ -47,6 +47,7 @@ app.use(createOneSubMiddleware({
   adminSecret: process.env.ADMIN_SECRET,   // enables admin + metrics routes
   logger: require('pino')(),               // any { info, warn, error } logger
   refundPolicy: 'immediate',               // 'immediate' (default) | 'until_expiry'
+  metricsCacheTtlSeconds: 30,              // 30 (default) | 0 to disable
 }));
 
 app.listen(4100);

package/dist/__tests__/apple-jws-cache.test.d.ts

@@ -0,0 +1,16 @@
+/**
+ * decodeJws — the cached chain-verification wiring.
+ *
+ * The success path cannot be exercised here: a chain that passes
+ * `verifyAppleCertChain` must be signed by Apple's private keys, and the
+ * verifier correctly refuses everything else. The cache's own behaviour is
+ * tested in isolation in `verified-key-cache.test.ts` (with an injected
+ * verifier). What this file pins down is the part that only the real function
+ * can show — that introducing a cache did not weaken rejection:
+ *
+ *   - a chain that fails verification is rejected EVERY time, not remembered
+ *   - a missing x5c is still rejected
+ *   - `skipVerification` still bypasses the whole path
+ */
+export {};
+//# sourceMappingURL=apple-jws-cache.test.d.ts.map

package/dist/__tests__/apple-jws-cache.test.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"apple-jws-cache.test.d.ts","sourceRoot":"","sources":["../../src/__tests__/apple-jws-cache.test.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG"}

package/dist/__tests__/metrics-aggregate.test.d.ts

@@ -0,0 +1,10 @@
+/**
+ * metrics-aggregate — the reduction behind every /onesub/metrics/* response.
+ *
+ * These semantics were previously only reachable through four HTTP handlers, so
+ * the fiddly parts (inclusive window edges, UTC bucket assignment, which records
+ * a distribution counts) had no direct coverage. They do now, and they are the
+ * contract any future SQL-side aggregation has to reproduce.
+ */
+export {};
+//# sourceMappingURL=metrics-aggregate.test.d.ts.map

package/dist/__tests__/metrics-aggregate.test.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"metrics-aggregate.test.d.ts","sourceRoot":"","sources":["../../src/__tests__/metrics-aggregate.test.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG"}

package/dist/__tests__/metrics-cache.test.d.ts

@@ -0,0 +1,11 @@
+/**
+ * createMetricsCache — the freshness bound on aggregate metrics responses.
+ *
+ * Every metrics endpoint reduces the whole store, so this cache is what stops a
+ * dashboard refresh loop from re-scanning it. The behaviours worth pinning down
+ * are the ones that would either defeat the purpose (a key that never repeats)
+ * or serve something wrong (a stale hit past its TTL, a shared entry between
+ * unrelated stores, a remembered failure).
+ */
+export {};
+//# sourceMappingURL=metrics-cache.test.d.ts.map

package/dist/__tests__/metrics-cache.test.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"metrics-cache.test.d.ts","sourceRoot":"","sources":["../../src/__tests__/metrics-cache.test.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG"}

package/dist/__tests__/purchase-product-lookup.test.d.ts

@@ -0,0 +1,17 @@
+/**
+ * Product-scoped purchase lookup — `PurchaseStore.getPurchasesForProduct`.
+ *
+ * Non-consumable validation used to read a user's entire purchase history and
+ * filter it in process, so an account with a long consumable history paid for
+ * every one of those rows on each lifetime-product purchase. The optional
+ * store method pushes the filter into an index instead.
+ *
+ * Covered here:
+ *   - the store contract, including the most-recent-first ordering all three
+ *     built-in stores must agree on
+ *   - that the route actually uses the index-backed method when a store has one
+ *     (responses are identical either way, so only a call count shows it)
+ *   - that a store without the method still works, since it is optional
+ */
+export {};
+//# sourceMappingURL=purchase-product-lookup.test.d.ts.map

package/dist/__tests__/purchase-product-lookup.test.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"purchase-product-lookup.test.d.ts","sourceRoot":"","sources":["../../src/__tests__/purchase-product-lookup.test.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG"}

package/dist/__tests__/verified-key-cache.test.d.ts

@@ -0,0 +1,18 @@
+/**
+ * VerifiedKeyCache — the memo behind Apple x5c chain verification.
+ *
+ * This cache sits directly on a security boundary: it decides when an
+ * expensive chain verification may be skipped. The real Apple path cannot be
+ * driven end-to-end in tests (a passing chain must be signed by Apple's private
+ * keys, and `verifyAppleCertChain` correctly refuses anything else), so the
+ * cache takes its verification as an injected function and the invariants are
+ * tested here directly:
+ *
+ *   - a hit skips verification, a miss does not
+ *   - every input participates in the entry identity (chain AND alg)
+ *   - a failed verification is never remembered
+ *   - no entry outlives the certificate chain that produced it
+ *   - eviction never hands back a stale key
+ */
+export {};
+//# sourceMappingURL=verified-key-cache.test.d.ts.map

package/dist/__tests__/verified-key-cache.test.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"verified-key-cache.test.d.ts","sourceRoot":"","sources":["../../src/__tests__/verified-key-cache.test.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;GAeG"}

package/dist/http.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"http.d.ts","sourceRoot":"","sources":["../src/http.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAEH,oDAAoD;AACpD,eAAO,MAAM,wBAAwB,QAAS,CAAC;AAE/C;;;;GAIG;AACH,wBAAsB,gBAAgB,CACpC,KAAK,EAAE,WAAW,GAAG,GAAG,EACxB,IAAI,CAAC,EAAE,WAAW,EAClB,SAAS,SAA2B,GACnC,OAAO,CAAC,QAAQ,CAAC,CAkBnB"}
+{"version":3,"file":"http.d.ts","sourceRoot":"","sources":["../src/http.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAEH,oDAAoD;AACpD,eAAO,MAAM,wBAAwB,QAAS,CAAC;AAE/C;;;;GAIG;AACH,wBAAsB,gBAAgB,CACpC,KAAK,EAAE,WAAW,GAAG,GAAG,EACxB,IAAI,CAAC,EAAE,WAAW,EAClB,SAAS,SAA2B,GACnC,OAAO,CAAC,QAAQ,CAAC,CA2BnB"}