@owf/eudi-tl 0.4.0-alpha-20260901082001

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 reasonable and customary use in 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 [yyyy] [name of copyright owner]
+
+   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/README.md

@@ -0,0 +1,217 @@
+# @owf/eudi-tl
+
+[![npm version](https://img.shields.io/npm/v/@owf/eudi-tl)](https://npmjs.com/package/@owf/eudi-tl)
+[![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://github.com/openwallet-foundation-labs/identity-common-ts/blob/main/LICENSE)
+
+Parse and verify **ETSI TS 119 612** XML Trusted Lists (`TrustServiceStatusList`)
+and expose normalized trust anchors.
+
+It is the XML counterpart of [`@owf/eudi-lote`](https://www.npmjs.com/package/@owf/eudi-lote)
+(ETSI TS 119 602, JSON): both formats resolve to the same normalized notion of a
+trust anchor, so a verifier can consume either and, for example, derive AKIs
+(SubjectKeyIdentifiers) to send to a wallet.
+
+## Why
+
+EUDI-context trust lists are published as **TS 119 602 (LoTE, JSON)**, but many
+existing trust services are published as classic **TS 119 612 (XML)** — both the
+standard eIDAS national lists (e.g. `TSLType/EUgeneric`, `TrstSvc/Svctype/*`,
+`Svcstatus/*`) and other profiled lists. The parser and signature verification
+are agnostic to the concrete URIs; profile-specific expectations are supplied by
+the caller as a `ProfileRule`.
+
+## Specification Reference
+
+- [ETSI TS 119 612](https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.03.01_60/ts_119612v020301p.pdf) - Trusted Lists
+
+## Installation
+
+```bash
+npm install @owf/eudi-tl
+# or
+pnpm add @owf/eudi-tl
+```
+
+## Usage
+
+### Loading a trusted list (verify, then parse)
+
+```typescript
+import {
+  ACTIVE_SERVICE_STATUSES,
+  loadTrustedList,
+  getTrustAnchors,
+} from '@owf/eudi-tl';
+
+// Verify the list's XAdES signature, then parse it. Pins the scheme operator
+// certificate(s) so a list signed by some other key fails closed.
+const trustedList = await loadTrustedList(xml, {
+  trustAnchors: [schemeOperatorCertDer],
+});
+
+// Flatten to individual anchors, keeping only active (granted) services.
+const anchors = getTrustAnchors(trustedList, {
+  serviceStatus: ACTIVE_SERVICE_STATUSES,
+});
+
+for (const anchor of anchors) {
+  // anchor.certificate          — base64 DER, when the list embeds one
+  // anchor.subjectKeyIdentifier — lowercase hex, for AKI queries
+  // anchor.serviceTypeIdentifier / anchor.serviceStatus / anchor.providerName
+}
+```
+
+### Following the EU hierarchy (LOTL → national lists)
+
+The EU **List of Trusted Lists** is the root of the eIDAS hierarchy: it points
+to every national list and publishes, for each one, the certificate(s) that list
+is signed with. So only the LOTL's own signers have to be pinned — the anchors
+of the national lists come from the LOTL itself:
+
+```typescript
+import {
+  getEuLotlTrustAnchors,
+  getPointerSigningCertificates,
+  loadEuLotl,
+  loadTrustedList,
+} from '@owf/eudi-tl';
+
+// Verified against the LOTL signing certificates shipped with this package.
+const lotl = await loadEuLotl(lotlXml);
+
+// The Spanish list's anchors, as published by the LOTL.
+const anchors = getPointerSigningCertificates(lotl, { schemeTerritory: 'ES' });
+const esList = await loadTrustedList(esXml, { trustAnchors: anchors });
+```
+
+`loadEuLotl` verifies the signature against `getEuLotlTrustAnchors()` and checks
+the `TrustedListProfiles.euLotl` profile. Pass your own `trustAnchors` to
+override the shipped set.
+
+#### Why the LOTL signers are pinned, and how to update them
+
+The shipped set (`EU_LOTL_SIGNING_CERTIFICATES`, with its
+`EU_LOTL_ANCHORS_PROVENANCE`) is the one out-of-band anchor the hierarchy needs:
+it cannot be bootstrapped from the LOTL itself, since a forged list would carry
+a forged self-pointer. The European Commission publishes it in the Official
+Journal, which the provenance record links.
+
+Those certificates rotate, so a deployment can stay current without waiting for
+a release of this package:
+
+1. pass your own `trustAnchors`, e.g. from configuration;
+2. read the currently published set from a verified LOTL's self-pointer and
+   persist it — a rotation is always announced in a list that is still signed by
+   the previous generation of keys:
+
+   ```typescript
+   const current = getPointerSigningCertificates(lotl, {
+     tslType: TSLType.EUlistofthelists,
+   });
+   ```
+
+3. if the pinned set has fallen behind entirely, follow the pivot LOTLs
+   advertised in the list's `SchemeInformationURI`.
+
+`scripts/refresh-lotl-anchors.mts` regenerates the shipped constant from the
+live LOTL, verifying it against the currently pinned set first.
+
+### Parsing without signature verification
+
+`parseTrustedList` performs no signature check — use it for lists whose
+authenticity is established elsewhere, or for inspection:
+
+```typescript
+import { parseTrustedList, validateTrustedList } from '@owf/eudi-tl';
+
+const trustedList = parseTrustedList(xml);
+const { valid, errors } = validateTrustedList(trustedList);
+```
+
+### Verifying the signature only
+
+```typescript
+import { verifyTrustedListSignature } from '@owf/eudi-tl';
+
+const { signerCertificateBase64 } = await verifyTrustedListSignature(xml, {
+  trustAnchors: [schemeOperatorCertDer], // optional but recommended
+});
+```
+
+Without `trustAnchors`, only the cryptographic validity of the enveloped
+signature is checked — that proves integrity, not trust. Production callers
+should always pin the scheme operator certificate(s).
+
+Verification uses the global Web Crypto API by default. To run it through a
+reviewed or policy-constrained engine ("bring your own crypto"), install your
+implementation once during start-up:
+
+```typescript
+import { setTrustedListCrypto } from '@owf/eudi-tl';
+
+setTrustedListCrypto(myWebCrypto);
+```
+
+The engine is process-wide by necessity, not by design: xadesjs exposes a
+single global crypto engine rather than a per-call context
+([xmldsigjs#119](https://github.com/PeculiarVentures/xmldsigjs/issues/119)).
+A per-verification option would look isolated while still swapping that global,
+so concurrent verifications with different engines would race — hence the
+explicit setter. Once installed, an engine is never silently replaced by the
+global one.
+
+### Validating against a profile
+
+Profiled ecosystems constrain the `TSLType` and the service type / status URIs
+a list may use. The engine stays profile-agnostic — supply the constraints as a
+`ProfileRule`:
+
+```typescript
+import { validateTrustedListProfile } from '@owf/eudi-tl';
+
+const result = validateTrustedListProfile(trustedList, {
+  name: 'my-profile',
+  tslType: 'https://example.org/lists/tsl-type',
+  serviceTypes: ['https://example.org/service-type/issuance'],
+  serviceStatuses: ['https://example.org/service-status/active'],
+});
+```
+
+For common ecosystems, ready-made rules ship as `TrustedListProfiles` so you
+don't have to hand-write the URIs:
+
+```typescript
+import { TrustedListProfiles, validateTrustedListProfile } from '@owf/eudi-tl';
+
+// EU LOTL, generic eIDAS national list, or EU Age Verification.
+validateTrustedListProfile(trustedList, TrustedListProfiles.ageVerification);
+```
+
+A profile is an allowlist (matched after the structural schema): the `TSLType`
+must match and every service type / status must be permitted. That fits curated,
+homogeneous lists (e.g. Age Verification) directly; `euGeneric` therefore permits
+all standard ETSI statuses and qualified service types — including the
+withdrawn/ceased entries national lists retain — rather than narrowing to active
+CAs. Narrow further with your own `ProfileRule` when you need to.
+
+## Error Handling
+
+All failures throw a subclass of `TrustedListException`:
+
+- `TrustedListParseException` — the XML is not a well-formed TS 119 612 list
+- `TrustedListSignatureException` — the signature is missing, invalid, or not
+  signed by a pinned trust anchor. Treat this as fail-closed.
+
+When a failure wraps an underlying error (e.g. a crypto error during
+verification), it is preserved on the exception's `cause`.
+
+## Test Fixtures
+
+The test suite uses two small synthetic lists generated by
+`scripts/generate-test-fixtures.mts`: an unsigned list exercising the parser
+and a signed sample (throwaway self-signed test certificates) exercising XAdES
+verification. The suite only verifies signatures — it never signs.
+
+## License
+
+Apache-2.0