x402-conformance 1.2.1__tar.gz

x402_conformance-1.2.1/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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.

x402_conformance-1.2.1/NOTICE

@@ -0,0 +1,7 @@
+x402-conformance
+Copyright 2026 Ryan Gillespie / Optitransfer
+
+Licensed under the Apache License, Version 2.0 (see LICENSE).
+
+This project tests implementations of the x402 protocol (https://github.com/coinbase/x402). It contains no code
+from that project; check identifiers and error codes are quoted from its public specification for reference.

x402_conformance-1.2.1/PKG-INFO

@@ -0,0 +1,288 @@
+Metadata-Version: 2.4
+Name: x402-conformance
+Version: 1.2.1
+Summary: Experimental conformance and safety checks for x402 V2 facilitators and resource servers, Solana first
+Author: Ryan Gillespie / Optitransfer
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/atsp-protocol/x402-conformance
+Project-URL: Documentation, https://github.com/atsp-protocol/x402-conformance/blob/main/docs/SPEC.md
+Project-URL: Changelog, https://github.com/atsp-protocol/x402-conformance/blob/main/CHANGELOG.md
+Project-URL: Issues, https://github.com/atsp-protocol/x402-conformance/issues
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Dynamic: license-file
+
+# x402 Conformance
+
+**Prove your x402 payments can't double-credit, credit too early or credit on a broken answer, in one CI step.**
+
+[![ci](https://github.com/atsp-protocol/x402-conformance/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/atsp-protocol/x402-conformance/actions/workflows/ci.yml)
+[![release](https://img.shields.io/github/v/release/atsp-protocol/x402-conformance)](https://github.com/atsp-protocol/x402-conformance/releases/latest)
+[![GitHub Marketplace](https://img.shields.io/badge/Marketplace-x402%20Conformance-blue?logo=github)](https://github.com/marketplace/actions/x402-conformance)
+[![licence](https://img.shields.io/github/license/atsp-protocol/x402-conformance)](LICENSE)
+[![Tested with x402-conformance](https://img.shields.io/badge/tested%20with-x402--conformance-2ea44f)](https://github.com/atsp-protocol/x402-conformance)
+
+An open set of conformance and safety checks for [x402](https://github.com/coinbase/x402) V2 facilitators and
+resource servers, starting with Solana. It checks the properties a seller's money depends on. It never signs, pays or
+touches mainnet. It complements x402 and its facilitators and doesn't replace them.
+
+**Experimental.** Passing a check is evidence about one property. It doesn't certify conformance to x402.
+— Ryan Gillespie, Optitransfer
+
+Project page with the checks and the latest results: https://atsp-protocol.github.io/x402-conformance/
+
+## Install
+
+| how | command | needs |
+|---|---|---|
+| GitHub Action | `uses: atsp-protocol/x402-conformance@v1` (see [below](#github-action)) | nothing |
+| Python CLI, one-off | `pipx run --spec "git+https://github.com/atsp-protocol/x402-conformance@v1" x402conf offline` | [pipx](https://pipx.pypa.io) or [uv](https://docs.astral.sh/uv/) |
+| Python CLI, installed | `pip install "git+https://github.com/atsp-protocol/x402-conformance@v1"` | Python 3.10+, no dependencies |
+| TypeScript runner | `git clone` this repo, then `cd ts && npm ci && npm run build` | Node 20+ |
+
+The packages aren't on PyPI (`x402-conformance`) or npm (`x402-conformance-svm`) yet, so `pip install x402-conformance`
+and `npx x402conf-svm` don't work today. Install from the release tag as shown. `@v1` follows the latest 1.x release;
+pin `@v1.2.0` if you want a fixed version.
+
+## Quickstart
+
+```
+pipx run --spec "git+https://github.com/atsp-protocol/x402-conformance@v1" x402conf offline
+uvx --from "git+https://github.com/atsp-protocol/x402-conformance@v1" x402conf live https://x402.org/facilitator
+```
+
+The first runs the F1-F9 safety suite against the built-in reference and fault-injected facilitator doubles. The
+second reads `GET /supported` from a facilitator and runs S1-S4. Both print JSON.
+
+## GitHub Action
+
+Save this as `.github/workflows/x402-conformance.yml`. It runs as is:
+
+```yaml
+name: x402 conformance
+on: [push, pull_request]
+jobs:
+  x402:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: atsp-protocol/x402-conformance@v1
+        with:
+          facilitators: https://x402.org/facilitator   # swap in your facilitator; GET /supported only
+```
+
+With no inputs it runs only the F1-F9 safety suite. `facilitators` adds the live `GET /supported` checks. To test
+your own resource server, point the Action at your paid route and give it the command that starts the server:
+
+```yaml
+      - uses: atsp-protocol/x402-conformance@v1
+        with:
+          resource-url: http://127.0.0.1:4020/paid
+          start: node server.js            # your server must use X402_FACILITATOR_URL as its facilitator
+```
+
+| input | default | what it does |
+|---|---|---|
+| `facilitators` | empty | Space-separated facilitator base URLs, checked with `GET /supported` only (S1-S4) |
+| `resource-url` | empty | Your paid route; the Action puts a facilitator double in front of it and runs R0-R9 |
+| `start` | empty | Command that starts your server; it receives `X402_FACILITATOR_URL` |
+| `port` | `4402` | Loopback port for the facilitator double |
+| `offline` | `true` | Run the F1-F9 suite against the reference and fault-injected doubles |
+| `results-dir` | `x402-conformance` | Where `live.json`, `resource-server.json` and `offline.json` are written |
+| `fail-on-error` | `true` | Fail the job when any error-severity check fails |
+
+| output | value |
+|---|---|
+| `result` | `pass` when every requested check passed, otherwise `fail` |
+| `results-dir` | the directory holding the results JSON |
+| `sarif` | `<results-dir>/x402-conformance.sarif`, SARIF 2.1.0 of the failed checks |
+| `junit` | `<results-dir>/junit.xml`, one test case per check |
+
+**Example job summary** (abridged):
+
+```
+## x402 Conformance: pass
+| target                       | check                                                         | result |
+| https://x402.org/facilitator | S1 SupportedResponse shape: kinds[], extensions[], signers{}  | pass   |
+| https://x402.org/facilitator | S4 Solana exact kinds advertise a valid extra.feePayer ...    | pass   |
+| reference double             | F3 the same payload settled twice succeeds at most once ...   | pass   |
+| reference double             | F9 a 503, non-JSON or truncated /settle answer is never ...   | pass   |
+| fault-injected doubles       | every fault caught by at least one check                      | pass   |
+```
+
+**Failures in code scanning.** Every failed check can show up in your repo's Security tab, with a link to what
+failed and how to fix it. Add `permissions: { security-events: write, contents: read }` to the job, `id: x402` and
+`fail-on-error: false` to the step above, then:
+
+```yaml
+      - uses: github/codeql-action/upload-sarif@v3
+        if: always()
+        with:
+          sarif_file: ${{ steps.x402.outputs.sarif }}
+          category: x402-conformance
+      - run: test "${{ steps.x402.outputs.result }}" = pass
+```
+
+The `junit` output works with any JUnit test-report viewer.
+
+## CLI
+
+```
+x402conf live https://x402.org/facilitator     # S1-S4, GET /supported only
+x402conf offline                               # F1-F9 against the reference and fault-injected doubles
+x402conf report --dir DIR --sarif out.sarif --junit junit.xml
+x402conf devnet --faults --keys DIR            # F1-F6 over real /verify and /settle on Solana devnet
+```
+
+`live` and `offline` print JSON with one entry per check (`check`, `pass`, `severity`, `detail`). Save them as
+`live.json` and `offline.json` in one directory and `report` converts them to SARIF and JUnit, printing a one-line
+summary such as `{"checks": 14, "failed": 0, "failed_ids": []}`. `devnet` runs against a self-hosted reference
+facilitator on loopback with throwaway keys from `--keys`, and refuses any other facilitator unless you pass
+`--operator-permission` with the operator's written permission. It needs Node 20+ and a funded devnet fee payer;
+[evidence/devnet](evidence/devnet) shows a full run.
+
+**Exit codes.**
+
+| command | 0 | non-zero |
+|---|---|---|
+| `x402conf offline` | the reference double passes every check and every fault-injected double is caught | `1` otherwise |
+| `x402conf live` | always, even when a check fails or the facilitator can't be reached | read the `pass` fields, or use the Action, which does |
+| `x402conf report` | the reports were written | `2` when the directory holds no results JSON |
+| `x402conf devnet` | the facilitator under test passes every check, and with `--faults` every fault-injected build is caught | `1` otherwise (the current reference exits `1` on F4, see [Results](#results)) |
+| `x402conf-svm probe` (TypeScript) | R0-R9 all pass | `1` when a check fails, `2` on an error |
+
+Usage errors exit `2`.
+
+**TypeScript runner** for resource servers on `@x402/core` and `@x402/svm`, from a clone of this repo:
+
+```
+cd ts && npm ci && npm run build
+node dist/src/cli.js probe --resource http://127.0.0.1:4020/paid --start "node your-server.js" --out results.json
+```
+
+[ts/README.md](ts/README.md) explains what the double does for each of R0-R9.
+
+## What it catches
+
+**Live, read-only (`GET /supported`):**
+- **S1** the response is missing `kinds`, `extensions` or `signers`
+- **S2** a V2 network isn't written as a CAIP-2 ID
+- **S3** a Solana kind uses an old V1 name such as `solana-devnet` instead of the published ID
+- **S4** a Solana `exact` kind has no valid fee payer, or one that isn't a listed signer
+
+**Safety, against doubles, on devnet and in your resource server:**
+- **F1** a malformed payment is accepted instead of rejected
+- **F2** an underpayment or dust amount is accepted
+- **F3** the same payment is settled, or served, twice
+- **F4** a used memo or nonce is replayed in a new transaction
+- **F5** a payment counts as settled before it's confirmed, or `settlement_pending` comes without a transaction
+- **F6** a facilitator timeout or garbage answer turns into a credit
+- **F7** a pending payment retried with the same body never reaches its final result, or is credited more than once
+- **F8** a payment that failed on chain stays "pending" instead of failing
+- **F9** a 503, an HTML page or a truncated `/settle` answer is credited, or the payment can't be retried afterwards
+
+**Resource servers (R0-R9).** The TypeScript runner puts a facilitator double in front of your server and requests your
+paid route under each of the faults above. Your server must answer an unpaid request with a 402 and must not serve
+content on a timeout, a broken `/settle` answer, `settlement_pending`, a failure or a duplicate.
+
+[docs/SPEC.md](docs/SPEC.md) quotes the spec text behind every check, and [docs/FIXES.md](docs/FIXES.md) explains, for
+every check, what failed, why it matters and how to fix it.
+
+## Results
+
+### Live, 2026-10-20, `GET /supported` only
+
+| facilitator | HTTP | S1 | S2 | S3 | S4 | Solana kinds advertised |
+|---|---|---|---|---|---|---|
+| x402.dexter.cash | 200 | pass | pass | pass | pass | exact (mainnet, devnet), tab, bridge |
+| facilitator.payai.network | 200 | pass | pass | pass | pass | exact and batch-settlement (mainnet, devnet) |
+| x402.org/facilitator | 200 | pass | pass | pass | pass | exact (devnet) |
+
+Raw bodies, `run.json` and `SHA256SUMS` are in [evidence/2026-10-20](evidence/2026-10-20).
+
+### Devnet, 2026-10-20, F1-F6 over real `/verify` and `/settle`
+
+I ran F1 to F6 on Solana devnet against my self-hosted reference facilitator (`@x402/core` and `@x402/svm` 2.28.0),
+then against fault-injected builds of it.
+
+| facilitator | F1 | F2 | F3 | F4 | F5 | F6 |
+|---|---|---|---|---|---|---|
+| self-hosted reference, `@x402/svm` 2.28.0 | pass | pass | pass | **fail** | pass | pass |
+
+F4 fails because the reference facilitator deduplicates by transaction but not by memo, so two different
+transactions with the same memo both settled. The payer paid twice, so the seller lost nothing, but a resource server
+that ties one purchase to one memo has to enforce that itself. Every fault-injected build was caught by the check
+it targets. Transaction links, the full `run.json` and its hash are in [evidence/devnet](evidence/devnet). Results for
+other facilitators go in the [facilitator matrix](docs/MATRIX.md), and I run them against a third party only with the
+operator's permission.
+
+## How this repo is verified
+
+Scope and acceptance criteria live in [`proofline.json`](proofline.json), a [Proofline](https://github.com/Optitransfer/proofline)
+contract. It's signed with my owner key: the signature is in `proofline.json.sig` and the public key is pinned in
+[`guard/owner.pub`](guard/owner.pub). On every push to `main` and on every pull request, CI checks that signature and then runs `tools/vv.py`, which checks
+every acceptance criterion and uploads a receipt ([docs/VV.md](docs/VV.md)). Any change to the contract has to be
+re-signed before CI passes again. You can check the signature yourself from a clone:
+
+```
+node tools/verify-sig.mjs                                       # no dependencies; exits 0 when the signature matches
+npx -y @optitransfer/proofline@next contract verify-sig         # the Proofline CLI (Node 22+), same check
+```
+
+The Lean 4 models in [`lean/`](lean) cover the credit rule, nonces, timeouts, `settlement_pending` reconciliation and
+concurrent settles. They use only standard axioms and contain no `sorry`. They model the rule the suite checks, not any
+facilitator's code.
+
+## Add the badge
+
+If your project runs the suite in CI, add this to your README:
+
+```markdown
+[![Tested with x402-conformance](https://img.shields.io/badge/tested%20with-x402--conformance-2ea44f)](https://github.com/atsp-protocol/x402-conformance)
+```
+
+## Who uses it
+
+No public users yet. I only list a user once they've said so publicly. If you run it, open an issue and I'll add you
+here and to [docs/ADOPTION.md](docs/ADOPTION.md).
+
+**Free run for your project.** Open an issue with your repo or facilitator URL and I'll run the suite against it,
+post the results, and send a tests-only pull request with the Action and badge. It's free, with no conditions.
+
+## Managed services
+
+The core is free and stays free. If you'd rather not run it yourself, or you need more than the open suite, I offer:
+- **Hosted continuous monitoring** of your live endpoints, with alerts on regressions
+- **Signed conformance reports** for each release, with a public verify link
+- **Custom checks** for your scheme, chain or extensions
+- **Priority support** with an agreed response time
+
+The first three customers get design-partner pricing. Monitoring is a monthly subscription, reports are priced per
+release, and custom checks are fixed-scope work quoted up front. Details are in [docs/MANAGED.md](docs/MANAGED.md). To get
+in touch, open a [Managed services enquiry](https://github.com/atsp-protocol/x402-conformance/issues/new?template=managed-services.yml)
+or email data@optitransfer.ch.
+
+## Safety
+
+The suite holds no keys of yours and never signs or pays. Live mode is GET-only, and that's tested. The devnet
+runner refuses mainnet and any third-party facilitator without written permission.
+
+## Security
+
+Please report vulnerabilities through GitHub private vulnerability reporting
+([Security → Report a vulnerability](https://github.com/atsp-protocol/x402-conformance/security/advisories/new)), not in
+a public issue. When the suite finds a failing safety check in someone else's facilitator, I tell the operator
+privately first. The full policy is in [SECURITY.md](SECURITY.md).
+
+## Contributing
+
+Issues and pull requests are welcome, and new checks especially. Propose one with the check-proposal issue template,
+quoting the x402 spec text it rests on. Every check needs a test that fails against a faulty double and passes against
+the reference. [CONTRIBUTING.md](CONTRIBUTING.md) lists the local checks to run before you push, and everyone taking
+part follows the [Code of Conduct](CODE_OF_CONDUCT.md). Changes are listed in [CHANGELOG.md](CHANGELOG.md).
+
+## Licence
+
+Apache-2.0. See [LICENSE](LICENSE) and [NOTICE](NOTICE) (Ryan Gillespie / Optitransfer).