@hesohq/verify-wasm 0.5.1-dev.131 → 0.5.1-dev.135

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/heso_wasm.d.ts CHANGED
@@ -579,9 +579,12 @@ export function validateNoFloorBypass(rules_json: string): void;
579
579
  * `verdict = "Malformed:…"`. This is the browser replacement for the
580
580
  * `verifyReceipt` function in `crypto.ts`, backed by the SAME Rust JCS +
581
581
  * BLAKE3 + Ed25519 core as Node for canonicalization, hashing, and signature
582
- * verification. NOTE: this is NOT byte-identical to Node for EVERY receipt
583
- * the `tsa` feature is OFF here, so a TIME-ANCHORED receipt that Node verifies
584
- * against its TSA stack is handled differently on the browser surface.
582
+ * verification. The `tsa` feature is ON here, so a TIME-ANCHORED receipt is
583
+ * verified against the SAME RFC-3161 trusted-time stack Node uses the proof
584
+ * page can now actually verify an anchor (rather than blanket reporting
585
+ * TimeAnchorUnverifiable). Verification stays fail-closed: an anchor is
586
+ * accepted only if its token chains to a pinned TSA root; any anchor that does
587
+ * not still resolves to TimeAnchorUnverifiable.
585
588
  */
586
589
  export function verifyActionReceipt(receipt_bytes: Uint8Array): ActionVerdict;
587
590
 
package/heso_wasm.js CHANGED
@@ -1862,9 +1862,12 @@ export function validateNoFloorBypass(rules_json) {
1862
1862
  * `verdict = "Malformed:…"`. This is the browser replacement for the
1863
1863
  * `verifyReceipt` function in `crypto.ts`, backed by the SAME Rust JCS +
1864
1864
  * BLAKE3 + Ed25519 core as Node for canonicalization, hashing, and signature
1865
- * verification. NOTE: this is NOT byte-identical to Node for EVERY receipt
1866
- * the `tsa` feature is OFF here, so a TIME-ANCHORED receipt that Node verifies
1867
- * against its TSA stack is handled differently on the browser surface.
1865
+ * verification. The `tsa` feature is ON here, so a TIME-ANCHORED receipt is
1866
+ * verified against the SAME RFC-3161 trusted-time stack Node uses the proof
1867
+ * page can now actually verify an anchor (rather than blanket reporting
1868
+ * TimeAnchorUnverifiable). Verification stays fail-closed: an anchor is
1869
+ * accepted only if its token chains to a pinned TSA root; any anchor that does
1870
+ * not still resolves to TimeAnchorUnverifiable.
1868
1871
  * @param {Uint8Array} receipt_bytes
1869
1872
  * @returns {ActionVerdict}
1870
1873
  */
package/heso_wasm_bg.wasm CHANGED
Binary file
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@hesohq/verify-wasm",
3
- "version": "0.5.1-dev.131",
3
+ "version": "0.5.1-dev.135",
4
4
  "description": "HESO Enterprise trust layer — browser WASM verify-only surface (ESM)",
5
5
  "type": "module",
6
6
  "scripts": {