@val-protocol/qes-validator 0.1.0

package/CHANGELOG.md

@@ -0,0 +1,16 @@
+# @val-protocol/qes-validator — CHANGELOG
+
+## 0.1.0 — 2026-06-30 — first release (Profile C BYO validator)
+
+- **Pure-JS eIDAS QES validator — zero runtime dependencies, no DSS.** Validates a brought qualified
+  signature for VAL Profile C (the bring-your-own-signature arm of ADR 0063): auto-routes **CAdES**
+  (`.p7m`, detached or enveloped) vs **JAdES** (JWS), binds the signature to the grant
+  (`messageDigest == SHA-256(canonical)`), builds the X.509 path, checks ETSI EN 319 412 QcStatements,
+  and resolves trust against the live EU **LOTL** (List of Trusted Lists).
+- **Honest structured verdict (`QesValidationReport`).** `status` (qualified / not_qualified /
+  indeterminate) + `subIndication` (`HASH_FAILURE`, `SIG_CRYPTO_FAILURE`, `FORMAT_FAILURE`,
+  `ANCHOR_NOT_ON_TRUSTED_LIST`, `CHAIN_INCOMPLETE`, …), `adesLevel`, and the eIDAS natural-person
+  `signerIdentity` — surfaced verbatim for the relying party's offline call, never collapsed to "failed".
+- **Exports:** `validateQes`, `matchGrantedCaQc`. Dual ESM + CJS.
+- Supersedes ADR 0063 S1's "wrap EU DSS (Java sidecar)" for the BYO arm — this validator is
+  dependency-light pure-JS. The CSC orchestrated-ceremony arm remains parked pending CSC/MultiSign access.

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for describing the origin of the Work and
+      reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 RIGA Solutions
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,13 @@
+@val-protocol/qes-validator
+Copyright 2026 RIGA Solutions
+
+This product includes software originally developed by RIGA Solutions as the
+reference QES (eIDAS qualified electronic signature) validator for the
+Verifiable Authorization Lineage (VAL) protocol — Profile C.
+Project home: https://github.com/val-protocol/verifiable-authorization-lineage
+
+Licensed under the Apache License, Version 2.0 (the "License"); you may not
+use this file except in compliance with the License. You may obtain a copy
+of the License at:
+
+    http://www.apache.org/licenses/LICENSE-2.0

package/README.md

@@ -0,0 +1,78 @@
+# @val-protocol/qes-validator
+
+**Not published.** Caller-side, **no-DSS, pure-JS** eIDAS **QES** (Qualified Electronic Signature)
+validator for VAL **Profile C**. See **ADR 0063**.
+
+`anchoring proves time; Profile C proves identity.` This package validates the qualified signature at the
+**root** of a VAL lineage — proving the human delegator is a **legally identified natural person** (eIDAS
+Art-25), not merely a device-key holder (Profile B).
+
+## Why a separate package
+
+The reference verifier `@val-protocol/chain-verifier` is **zero-dependency** (Charter §II — "verify
+without trusting RIGA"). QES validation (X.509 path-building, QcStatements, Trusted-List resolution) is
+not zero-dep, so it lives here. The core **consumes its verdict** — exactly as Pass 4 consumes a resolved
+`anchorTrust`. The relying party runs this validator themselves, so verification stays **trustless**.
+
+## No DSS, no server (the trustless point)
+
+A relying party verifies a VAL grant's qualified signature **without standing up a Java DSS** — this is
+pure JS (Node 18+ / browser-friendly via Web Crypto + `node:crypto` X509). It reuses
+`@val-protocol/anchor-lotl-resolver` for the LOTL→member-state pointer, and adds a **CA/QC-for-eSignatures**
+Trusted-List matcher beside the resolver's TSA/QTST one (a TSA hit is **never** counted as a
+qualified-eSignature hit).
+
+## Documented ETSI subset (honest scope)
+
+1. JWS/JAdES parse — ETSI TS 119 182-1
+2. signature-value verification over the JWS signing input via the embedded `x5c` — ETSI TS 119 102-1
+3. certificate-path build + verification leaf → issuer → trust anchor — ETSI TS 119 102-1
+4. qualification-status determination — ETSI TS 119 615: `QcCompliance` (0.4.0.1862.1.1) **and**
+   `QcType-eSign` (0.4.0.1862.1.6.1) in the signing cert **and** the issuer is a granted
+   **CA/QC-for-eSignatures** Trusted-List service at signing time.
+
+**Out of scope (DSS's job, not reimplemented):** per-certificate OCSP/CRL revocation, full AdES-LTA /
+archive-timestamp LTV. Revocation here is at Trusted-List **service-status** granularity (granted /
+withdrawn at signing time), not per-cert OCSP.
+
+## Precondition: complete certificate chain (no AIA chasing)
+
+The validator anchors a signature ONLY if the full path **leaf → … → TL-listed granted CA/QC service**
+is present in the JAdES `x5c` header or in `trust.intermediateHintsDer`. It does **not** fetch missing
+issuer certificates (no AIA / `caIssuers` chasing) — that would require a network call and break the
+offline/trustless model. DSS-emitted JAdES carries the full chain in `x5c`; a leaner non-DSS QTSP that
+emits a partial `x5c` (leaf only) will return **`status: 'not_qualified'`, `subIndication: 'CHAIN_INCOMPLETE'`**
+(supply the full chain, or pass the intermediates via `intermediateHintsDer`) — **never a false `qualified`**.
+This is distinct from `ANCHOR_NOT_ON_TRUSTED_LIST` (the chain WAS complete and reached a self-issued top
+that simply isn't a granted CA/QC service — e.g. an attacker's self-signed root).
+
+## Verdict — conclusive vs indeterminate, and per-signature keying
+
+`validateQes(input) → QesValidationReport`. `qualified: boolean` is the only field the core treats as the
+gate, and is `true` **only** on a conclusive positive. Everything else is `status: 'not_qualified'`
+(conclusive negative) or `status: 'indeterminate'` (could not conclude — e.g. LOTL unreachable, no trust
+anchor, CAdES input) — never a silent `qualified:true`. `signatureRef` (sha256-hex of the delegation
+signature bytes) lets the core match **this** report to **this** signature (per-signature matching), so
+distinct qualified delegations never borrow each other's verdict.
+
+```ts
+import { verifyValChain } from '@val-protocol/chain-verifier';
+import { validateQes } from '@val-protocol/qes-validator';
+
+const report = await validateQes({
+  signedCanonical,                 // the root ASSIGNMENT canonical bytes the QES was computed over
+  signature,                       // ValQesSignature { alg, signature } (detached JAdES)
+  validationTime: anchorGenTime,   // ADR 0062 anchor time for at-signing-time determination
+  trust: { tslXml, trustAnchorsDer }, // or { fetchLive: true } to pull the EU LOTL live
+});
+const result = await verifyValChain(rows, { qesValidation: { reports: [report] } });
+// result.conformanceProfile === 'C' and result.signature === 'green' when report.qualified === true
+```
+
+## Tests
+
+`npm test` — deterministic openssl fixtures (`test/fixtures/gen.sh`), no DSS, no network: the positive
+(real ES256 signature verified + cert-path + QcStatements + CA/QC TSL), and negatives (mangled sig,
+TSA-only issuer, withdrawn / granted-late service, no-ForeSignatures, wrong canonical, no anchor,
+CAdES → indeterminate). **Not proven here:** byte-compatibility with a real DSS-emitted JAdES (needs the
+infra-gated SSL.com artifact) — the fixtures are spec-shaped (sigD ObjectIdByURIHash) but synthetic.