@intyga/verify 0.0.0-bootstrap.0 → 1.0.0

package/CHANGELOG.md

@@ -0,0 +1,162 @@
+# Changelog
+
+All notable changes to `@intyga/verify` are documented here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versions follow [SemVer](https://semver.org/).
+
+## [Unreleased]
+
+## [1.0.0]
+
+- Packaging: disable source maps in the workspace build and clean old output before compiling,
+  matching the standalone build and the tarball's build-output-only contract.
+
+- Verify profile-carried WebAuthn audit signatures with caller-trusted signer keys, origin and RP ID.
+  Report explicit per-event signature status and key trust; add strict signature acceptance for
+  single and bulk evidence. Audit signature checks do not replace full approval-receipt verification.
+
+- **DIV/DEWP 1.0 pre-release correction (2026-09-27 review L15-L19, I7, I8):** signed timestamps
+  are parsed under one strict RFC 3339 grammar (four-digit year, uppercase `T`/`Z`, seconds, a 1-9
+  digit fraction, `Z` or `±hh:mm`, a date that exists, no leap second) instead of bare `Date.parse`,
+  which accepted date-only and zone-less values and rolled 30 February into March. `stableStringify`
+  refuses a string with an unpaired surrogate (`NonCanonicalValue`) instead of escaping it (DIV §4.1).
+  A WebAuthn `topOrigin` differing from `origin` is refused like `crossOrigin: true`.
+  `verifyPlatformReceipt` requires user verification even when `requireUserVerification: false` is
+  passed (DIV §5c.3). A key mapped to two DIDs counts once toward a quorum (DIV §4.4.6). A malformed
+  trust anchor (`approvers: {}`) refuses instead of throwing; `agentReceiptDigest` projects an absent
+  witness field to `null` and the chain verifiers refuse rather than throw. RSA-PSS anchors require a
+  32-byte salt and a 2048-bit modulus, and `signAnchor` now signs with a 32-byte salt (**breaking**
+  for RSA-PSS anchors signed with the maximum salt). Divergence evidence is held to the quorum's
+  seq-range and witness-time rules, and a Rekor entry establishes divergence only under pinned
+  submitter keys. Pinned in all five languages by the `verifierInputHardening` parity vectors; no canonical bytes change for valid input.
+- **DIV 1.0 pre-release correction (H1):** add `expected.requirement` (`RequirementFloor`:
+  `requiredApprovals`, optional `requesterCannotApprove` / `requireHardwareKey`) to
+  `verifyApprovalReceipt`, `verifyDelegation`, `verifyAgentAuthority` and the `agentAuthorityChain`
+  links, and export `WEAKER_REQUIREMENT_REASON`. The signed `requirement` is authored by the signers,
+  so one approver (possibly the requester) could self-compose a 1-of-1 receipt for a 3-of-3 four-eyes
+  action and it verified. A weaker signed requirement is now refused before any signature is counted
+  when the caller supplies its own rule (DIV §5 step 3d), on approval, offline, delegation and
+  agent-authority verification; the reason starts "signed requirement is weaker than the relying
+  party's policy". Omitting the floor keeps the previous behaviour, which proves only the quorum the
+  signers stated. No signed byte changes; shared parity vectors pin it in all five languages.
+- **DEWP evidence verification (1.0 pre-release correction, Sep 2026):** an entry that carries a
+  canonical preimage reads `tenantSeq` only from it (`null` ⇒ no counter) and fails when its
+  redaction record's counter disagrees; a tenant-bound entry fails in a bundle that declares no (or
+  another) tenant; a preimage under an unknown profile fails the bundle; a repeated leaf or `seq`, or
+  leaf counts inconsistent with each other or the checkpoint's `entryCount`, fail; a checkpoint with
+  no `chainHash`/`anchoredAt` is never anchored. New `trustedCheckpoints` (evidence) and
+  `trustedCheckpoint` (single proof) options take caller-held roots-file records: a contradicting
+  bundle checkpoint fails and anchors are held to the record; a single proof counts a Rekor/TSA anchor
+  only against one. `isWellFormedAnchor` requires `algorithm` ∈ ES256/Ed25519/RSA-PSS. Pinned in all
+  five languages by the `dewpEvidenceHardening` parity vectors.
+- **DIV 1.0 pre-release correction (PK-11):** under a signed `requireHardwareKey`, a WEBAUTHN witness
+  whose signed authenticatorData carries the Backup Eligible or Backup State flag no longer counts
+  toward the quorum (DIV §4.4.5 rule 6) — a relying party now catches an issuer that let a synced
+  passkey sign a hardware-pinned action. No signed byte changes; shared parity vectors pin it in all
+  five languages.
+- Add `verifyWebAuthnWitness(witness, expectation)`: the DIV §4.4.5 checks on ONE WebAuthn assertion
+  (payload binding, origin, RP ID, UP/UV, crossOrigin, signature under a caller-supplied COSE or SPKI
+  P-256 key) without a receipt around it — for re-verifying a single stored witness. It is the same
+  implementation every receipt verifier runs, not a copy, and it enforces no quorum, window or policy.
+- **Breaking (DEWP 1.0 pre-release correction):** the anchored preimage is now
+  `[dailyRoot, timestamp, issuer, algorithm, seqStart, seqEnd, chainHash]`; anchors lacking the
+  position fields never verify. External witness times (Rekor `integratedTime`, TSA `genTime`) must
+  fall within `maxAnchorLagSeconds` (default 86400) after — or 300 s before — the checkpoint's claimed
+  time; anchors must match the checkpoint's seq range, chain hash and `anchoredAt`; evidence-bundle
+  chain hashes are recomputed; verdicts expose per-issuer witness times; an optional pinned Rekor
+  submitter key is enforced. A supplied root is reported as `rootSource: "caller-supplied"` (was
+  `"independent"`).
+- A non-empty `allowedAaguids` is refused exactly like `requireHardwareKey`: bare-key witnesses do not
+  count and offline proofs are rejected (DIV §4.3.2/§5a.3).
+
+- Add optional OpenSSL 3 RFC 3161 verification with issuer-specific certificate pins, offline CRL policy, shared cross-language vectors and quorum/divergence integration.
+
+- Enforce DIV §5 identity trust for multi-approver quorums; preserve DIV §4.4.2 ES256
+  compatibility for absent/null/unknown witness labels, while refusing AUTO_APPROVED witnesses.
+- Validate DEWP protocol, version and declared hash/serialization/Merkle algorithms before
+  accepting proof or evidence bundles. Legacy numeric revisions 1/2 remain supported without
+  a protocol declaration. Shared cross-language fixtures cover these contracts.
+
+- Packaging: the published type entry is `dist/index.d.ts` (and `dist/approval-policy.d.ts` for
+  the subpath) instead of the raw `src/*.ts`. Pointing `types` at source made every consumer compile
+  this package under THEIR `tsconfig`: on `lib` below ES2022 that produced TS2550 on `Object.hasOwn`
+  and `Array.at` from inside the package, unfixable from the consumer side because `skipLibCheck`
+  only skips `.d.ts` files. `engines.node` is `>=18`, and a Node-18-targeted `lib` is exactly the
+  case that broke.
+- Packaging: the tarball is `dist` only — no `src`, no tests, no vectors, no source maps (24 files,
+  82.6 kB, down from 62 and 245 kB). The source shipped alongside the build could not verify it:
+  no `tsconfig.json` ships, so nobody could rebuild `dist` from it and compare, which made it an
+  audit artifact that bound nothing. The source, the vectors and a CI run of the full suite are in
+  the public repository, tagged at each released version; what binds a released tarball to that tag
+  is the passkey-signed approval receipt over its sha256, not a copy of the source. No runtime or
+  canonical-byte change.
+- **Wire format: DIV v1 agent intents now sign `action`, `agent`, `session`, `nbf`, and `exp` instead of ordinary `expiresAt`; `div-agent-authority` requires `parentReceiptHash` (null for a root).** Older §5b seals lacking that key cannot verify under this pre-release profile and must be re-sealed. All canonical producers, five verifier ports and vectors must move together; the ordinary HUMAN/SERVICE intent keeps `expiresAt`.
+
+- The shared approval-policy resolver supports internal tenant policy version 3: one `*` baseline, exact case-sensitive
+  action IDs, at most one rule per ID, and an explicit unknown-action choice. This changes no
+  canonical receipt bytes or historical verification.
+
+- Add the dependency-free `@intyga/verify/approval-policy` subpath for shared approval-rule
+  conflict checks. A higher-ranked rule cannot discard another matching constraint in strict mode.
+  This adds no fields to canonical receipt payloads and does not change historical signatures.
+
+- **Wire format: the DIV Intent Payload gained a REQUIRED `evidence` field, and it must be `null`.**
+  `div-intent-verification` and `div-offline-intent` now carry `"evidence":null` in the signed bytes
+  (DIV §4.3.4); `div-delegation`, `div-agent-authority` and `div-platform-intent` deliberately do
+  not. `null` is signed and load-bearing, exactly as `requester.attestation`'s null is: it is the
+  payload's explicit statement that the authorization was not conditioned on any external fact.
+  Verification refuses a payload whose `evidence` key is absent, and refuses any non-`null` value
+  rather than treating it as unconditioned — the same fail-closed-on-unknown rule as the
+  `signerClass` registry, and checked before Local Payload Reconstruction so an unsupported payload
+  shape does not surface as a parameter mismatch. Absent and `null` are distinguished explicitly;
+  collapsing them would make the check a no-op. All golden vectors were regenerated.
+
+- Align cross-language receipt and audit verification: platform receipts, agent-authority seals,
+  self-certifying DID trust, single/multi-event bundles, embedded ES256 signatures, tenant sequence
+  checks, checkpoint continuity, anchor quorum and Rekor. Shared executable fixtures cover valid
+  artifacts and refusals; no wire format changes.
+- Refuse unknown witness signature algorithms. Require identity-bound trust when the signed
+  `requesterCannotApprove` rule is set; key-only trust cannot enforce requester identity.
+- **`verifyRootsChain` range-checks the FIRST entry.** The non-integer and self-inverted seq-range
+  checks were gated on having a predecessor, so the first entry was never range-checked — and a
+  single-entry `roots.jsonl` (a new tenant, or the first day after a truncation) is exactly where
+  the first entry is the only one. Such a file verified clean here while Go and Rust refused it.
+  Only the overlap check is relational now. New `single-entry-inverted-seq-range` and
+  `single-entry-non-integer-seq-range` parity vectors pin it in all five ports.
+- Decide the `requesterCannotApprove` + key-set-anchor refusal BEFORE the witness loop. It sat
+  inside the loop, after a witness had matched, so a receipt where nothing matched reported "quorum
+  not met" instead of naming the trust-anchor shape. Verdict unchanged; reason now matches the
+  other four ports and DIV §5 step 3b.
+
+- Recheck cached delegation expiry when verifying an approval, using the same evaluation clock,
+  skew allowance and explicit forensic override as a fresh verification.
+- A configured DEWP anchor quorum now gates the single-proof `ok` verdict, including when anchor
+  material is missing. Both proof and evidence bundles refuse a configured policy without its
+  required key resolver.
+- Reject sparse JavaScript arrays instead of signing or accepting bytes for a different array.
+  Canonical bytes for valid JSON are unchanged across the language ports.
+- **`verifyEvidenceBundle` no longer reports false ANCHOR DIVERGENCE on a multi-day export.** The
+  caller's flat `anchors` list was offered as divergence evidence to every checkpoint root in the
+  bundle, so a genuine anchor for one day read as a conflicting anchor for another — a fatal verdict
+  on sound evidence. Caller anchors are now attributed to a checkpoint first, and `anchors` also
+  accepts the keyed form `{ [checkpointIdOrRoot]: SignedAnchor[] }` for an exact per-checkpoint
+  verdict. The flat form still works and still declares divergence for an anchor over a root the
+  bundle does not claim.
+- **Refuse a forward-dated offline proof or delegation (DIV §5a.3 rule 3, §5a.6 step 1).** The
+  window caps bounded a proof's WIDTH but never its POSITION, so a quorum-signed proof dated years
+  ahead with a compliant 60-minute (or 72-hour) window verified today and kept verifying until that
+  date. The check is unconditional — the audit/`allowExpired` override re-examines a proof that was
+  valid and has lapsed, and does not reach one dated in the future.
+- **Refuse a signed `requirement.requiredApprovals` below 1 (DIV §4.3.2).** §5 step 7's "at least
+  `requiredApprovals`" is satisfied vacuously by 0, so the minimum is now enforced explicitly
+  instead of by an undocumented floor.
+
+
+Initial public release.
+
+- Offline approval-receipt verification (ES256 and WebAuthn) against a caller-supplied trust
+  anchor — no INTYGA secret, no network. `AUTO_APPROVED` receipts are refused by default.
+- DIV canonical payload builders and verification codes, pinned by shared cross-language golden
+  vectors.
+- DEWP ledger verification: inclusion proofs with mandatory bounds checks, §5.2 anchor signatures,
+  §5.3 anchor-quorum evaluation, §5.4 checkpoint continuity chain, and evidence bundles.
+- Zero runtime dependencies (Node ≥ 18, `node:crypto` only).

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 2026 Janbjer Technologies AB
+
+   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.