capacity-attest 0.9.2 → 0.10.0

package/dist/freshness.d.ts

@@ -0,0 +1,32 @@
+/** The minimal shape this check needs — any object with the claim's `timestamp` field. */
+export interface TimestampedClaim {
+    timestamp: string;
+}
+export type FreshnessResult = {
+    fresh: true;
+} | {
+    fresh: false;
+    reason: "stale";
+    ageMs: number;
+} | {
+    fresh: false;
+    reason: "timestamp_in_future";
+    ageMs: number;
+} | {
+    fresh: false;
+    reason: "invalid_timestamp";
+};
+/**
+ * Checks a claim's own `timestamp` against `maxAgeMs`, as of `now`.
+ *
+ * Boundary is inclusive: a claim exactly `maxAgeMs` old is still fresh (`ageMs <= maxAgeMs`).
+ * A timestamp strictly in the future (ageMs < 0) is never "fresh" — that is not a freshness
+ * problem, it is a malformed-or-backdated claim, reported as its own distinct reason so a
+ * caller does not silently treat it as simply recent.
+ *
+ * Pure and synchronous: no network call, no state, nothing to feed with data. A timestamp
+ * comparison does not get "smarter" over time — it is a fixed rule, and that is deliberate:
+ * the whole point is that the verifier does not have to trust anything that changes.
+ */
+export declare function checkClaimFreshness(claim: TimestampedClaim, maxAgeMs: number, now?: Date): FreshnessResult;
+//# sourceMappingURL=freshness.d.ts.map

package/dist/freshness.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"freshness.d.ts","sourceRoot":"","sources":["../src/freshness.ts"],"names":[],"mappings":"AAaA,0FAA0F;AAC1F,MAAM,WAAW,gBAAgB;IAC/B,SAAS,EAAE,MAAM,CAAC;CACnB;AAED,MAAM,MAAM,eAAe,GACvB;IAAE,KAAK,EAAE,IAAI,CAAA;CAAE,GACf;IAAE,KAAK,EAAE,KAAK,CAAC;IAAC,MAAM,EAAE,OAAO,CAAC;IAAC,KAAK,EAAE,MAAM,CAAA;CAAE,GAChD;IAAE,KAAK,EAAE,KAAK,CAAC;IAAC,MAAM,EAAE,qBAAqB,CAAC;IAAC,KAAK,EAAE,MAAM,CAAA;CAAE,GAC9D;IAAE,KAAK,EAAE,KAAK,CAAC;IAAC,MAAM,EAAE,mBAAmB,CAAA;CAAE,CAAC;AAElD;;;;;;;;;;;GAWG;AACH,wBAAgB,mBAAmB,CAAC,KAAK,EAAE,gBAAgB,EAAE,QAAQ,EAAE,MAAM,EAAE,GAAG,GAAE,IAAiB,GAAG,eAAe,CAiBtH"}

package/dist/freshness.js

@@ -0,0 +1,39 @@
+// freshness.ts — a verifier-side staleness check over the claim's own, already-signed
+// `timestamp` field. Additive, same discipline as the rest of this package: no new schema
+// field, no issuer-maintained registry, nothing a verifier has to trust beyond the signature
+// itself. See README.md "Independently verifying a claim" for why `verifyClaim()` alone does
+// NOT check this: a cryptographically valid signature says nothing about how old the claim is.
+//
+// Background: x402-foundation/x402 issue #2833 (imokokok, 6 Nov 2026) describes the same gap
+// in a different design (a signed oracle verdict that stays byte-valid after the underlying
+// venue went stale) and proposes an issuer-maintained STALE registry. This module is the
+// alternative that needs no registry: every claim here already carries a mandatory timestamp
+// as part of what got signed (schema.ts), so the verifier can apply its own policy without
+// trusting anyone's ongoing diligence.
+/**
+ * Checks a claim's own `timestamp` against `maxAgeMs`, as of `now`.
+ *
+ * Boundary is inclusive: a claim exactly `maxAgeMs` old is still fresh (`ageMs <= maxAgeMs`).
+ * A timestamp strictly in the future (ageMs < 0) is never "fresh" — that is not a freshness
+ * problem, it is a malformed-or-backdated claim, reported as its own distinct reason so a
+ * caller does not silently treat it as simply recent.
+ *
+ * Pure and synchronous: no network call, no state, nothing to feed with data. A timestamp
+ * comparison does not get "smarter" over time — it is a fixed rule, and that is deliberate:
+ * the whole point is that the verifier does not have to trust anything that changes.
+ */
+export function checkClaimFreshness(claim, maxAgeMs, now = new Date()) {
+    const claimedAt = Date.parse(claim.timestamp);
+    if (Number.isNaN(claimedAt)) {
+        return { fresh: false, reason: "invalid_timestamp" };
+    }
+    const ageMs = now.getTime() - claimedAt;
+    if (ageMs < 0) {
+        return { fresh: false, reason: "timestamp_in_future", ageMs };
+    }
+    if (ageMs > maxAgeMs) {
+        return { fresh: false, reason: "stale", ageMs };
+    }
+    return { fresh: true };
+}
+//# sourceMappingURL=freshness.js.map

package/dist/freshness.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"freshness.js","sourceRoot":"","sources":["../src/freshness.ts"],"names":[],"mappings":"AAAA,sFAAsF;AACtF,0FAA0F;AAC1F,6FAA6F;AAC7F,6FAA6F;AAC7F,+FAA+F;AAC/F,EAAE;AACF,6FAA6F;AAC7F,4FAA4F;AAC5F,yFAAyF;AACzF,6FAA6F;AAC7F,2FAA2F;AAC3F,uCAAuC;AAavC;;;;;;;;;;;GAWG;AACH,MAAM,UAAU,mBAAmB,CAAC,KAAuB,EAAE,QAAgB,EAAE,MAAY,IAAI,IAAI,EAAE;IACnG,MAAM,SAAS,GAAG,IAAI,CAAC,KAAK,CAAC,KAAK,CAAC,SAAS,CAAC,CAAC;IAC9C,IAAI,MAAM,CAAC,KAAK,CAAC,SAAS,CAAC,EAAE,CAAC;QAC5B,OAAO,EAAE,KAAK,EAAE,KAAK,EAAE,MAAM,EAAE,mBAAmB,EAAE,CAAC;IACvD,CAAC;IAED,MAAM,KAAK,GAAG,GAAG,CAAC,OAAO,EAAE,GAAG,SAAS,CAAC;IAExC,IAAI,KAAK,GAAG,CAAC,EAAE,CAAC;QACd,OAAO,EAAE,KAAK,EAAE,KAAK,EAAE,MAAM,EAAE,qBAAqB,EAAE,KAAK,EAAE,CAAC;IAChE,CAAC;IAED,IAAI,KAAK,GAAG,QAAQ,EAAE,CAAC;QACrB,OAAO,EAAE,KAAK,EAAE,KAAK,EAAE,MAAM,EAAE,OAAO,EAAE,KAAK,EAAE,CAAC;IAClD,CAAC;IAED,OAAO,EAAE,KAAK,EAAE,IAAI,EAAE,CAAC;AACzB,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "capacity-attest",
-  "version": "0.9.2",
+  "version": "0.10.0",
   "description": "MCP server for capacity-delivery attestations: after an x402 payment for compute capacity (GPU-hours, storage, API credits, bandwidth), the paying agent leaves a signed, factual claim of what was actually delivered, so other agents can check a seller's delivery history before paying. No reputation score, no judgment, no financial instrument.",
   "keywords": [
     "mcp",