viafrei 0.0.2 → 0.0.9

package/CHANGELOG.md

@@ -0,0 +1,230 @@
+# Changelog
+
+All notable changes to this package are documented here. The format follows Keep
+a Changelog and the versions follow Semantic Versioning.
+
+## [0.0.9] - 2026-09-21
+
+The first release with code in it.
+
+`viafrei@0.0.2` on the registry is a three-file placeholder published to reserve
+the name; no code was ever shipped under it. npm versions are immutable, so the
+first release that ships anything is this one.
+
+**Why 0.0.9 and not 0.1.0.** This package is the client end of a hosted service,
+and a version that does not say which service it was built against is a version
+you have to look up. So the bridge tracks the platform: 0.0.9 is what the hosted
+endpoint runs today. Nothing was ever published as 0.1.0 and no tag was ever cut
+for it, so the number is free; the bridge will use it when the platform does.
+
+### Fixed
+
+- **The publish pipeline no longer depends on the calendar.** It installed
+  `npm@latest` before publishing, so the version of npm that built and uploaded
+  a release was whichever one npm had shipped most recently. npm 12 became
+  `latest`, changed `npm pack --json` from an array to an object keyed by
+  package name — a deliberate change, announced in npm's own source before it
+  landed — and the job broke with no commit here. The npm is pinned now
+  (`NPM_VERSION` in the publish workflow), the install is asserted rather than
+  assumed, and both shapes are read by one file, `scripts/npm-pack-json.mjs`,
+  which every caller goes through: the gate, its self-test, and the workflow
+  step that packs the tarball all used to parse that output by hand, three
+  copies of an assumption about a format none of them owns. A shape the reader
+  does not know is one sentence naming the npm version and pointing at the pin
+  — not a `TypeError` with a stack trace of absolute paths in a public log,
+  which is what the self-test did, and not the wrong exit code, which the gate
+  contract already forbids. The reader's cases are fixtures, so they hold under
+  an npm nobody has installed yet.
+
+- **`npx viafrei` started nothing.** The check for "was this file the program,
+  or was it imported" compared `process.argv[1]` with `import.meta.url` without
+  resolving symlinks. npm installs a `bin` as a symlink and every client starts
+  the package through it, so `argv[1]` was the link while Node had already
+  resolved the module's own URL to the target: the two never matched, the
+  process loaded the file, ran nothing and exited **0 with no output**, which
+  reads as a bridge that started and closed rather than as a failure. The entry
+  point is now compared both as given and resolved, so it holds under
+  `--preserve-symlinks-main` too. Found by installing the packed tarball into an
+  empty directory and running the installed command - the whole test suite
+  spawned the built file by its real path, which is the one way nobody starts
+  it, so 50 passing tests said nothing about the only invocation that exists.
+  The regression test spawns through a symlink and fails against the old check.
+
+- **The unreachable-endpoint line advised something that does not exist.** It
+  ended "check the URL, or pass `--url` for a different endpoint", which reads
+  as though another ViaFrei could be reached at another address. There is one,
+  it is hosted, and `--url` is for a proxy in front of it. The line now says to
+  check the network connection, and names `--url` only for the proxy case.
+
+### Added
+
+- **The bridge.** `npx viafrei` opens an MCP server on stdio and relays every
+  JSON-RPC message to a Streamable-HTTP MCP endpoint - requests, responses,
+  notifications and progress, in both directions, unchanged. It is a message
+  relay rather than a client/server pair, so a tool added on the server works
+  through it the same day without a release here.
+- **Configuration.** `--url` / `VIAFREI_MCP_URL` for the endpoint (a proxy in
+  front of the service, or the test suite's stub - the server itself is hosted
+  and cannot be run yourself), `--header` for a future API key, `--timeout` /
+  `VIAFREI_MCP_TIMEOUT_MS`, `--version`, `--help`. No telemetry, no analytics,
+  and no file written outside the OS temp directory.
+- **Honest failure.** An unreachable or refusing endpoint prints one line naming
+  the URL and the status and exits with a code that says which
+  (`3` unreachable, `4` the endpoint answered and this cannot continue,
+  `5` protocol mismatch, `2` bad usage, `1` anything else) - never a stack
+  trace. A protocol mismatch says which version the server speaks; an endpoint
+  that answers with something that is not MCP is told apart from one that
+  refuses; a session the server has forgotten ends the process instead of being
+  warned about for ever; and several failures in a row with nothing succeeding
+  in between end it too, so a client never keeps a bridge that cannot relay.
+- **Headers stay on the origin you chose.** Redirects are resolved by the bridge
+  rather than by `fetch`: same-origin hops are followed with the headers,
+  cross-origin redirects are refused with one line naming both ends. `fetch`
+  drops `Authorization` across origins and nothing else, so an API key sent as
+  `X-Api-Key` would otherwise have travelled wherever the server pointed.
+- **Offline test suite.** Every test runs against a stub MCP server the test
+  starts itself; nothing contacts the public endpoint or any provider.
+- **A publish-hygiene gate that runs in CI**, against the built tarball rather
+  than the source tree - five checks: the tarball is the package and only the
+  package; no embedded sources; no platform content; **no lifecycle script in
+  the published manifest** (npm runs those by itself on every machine that
+  installs the package - ours included, so there is no `prepack` here); and
+  **every dependency judged by what it resolves to**, not by its name, because a
+  git URL under an innocent name is still a git URL. The scan decodes base64,
+  hex, percent-encoding, JavaScript escapes and concatenated string literals,
+  and prints what it still cannot see on every run - computed from the
+  thresholds the decoders actually use, so it cannot claim a coverage the code
+  does not have. Its self-test builds one poisoned tarball per rule the gate
+  reads - every lifecycle script, every forbidden file name, every required
+  file, every pattern, every number, every encoding at every alignment - plus
+  one mutated ruleset per refusal the rules can produce, run against BOTH legs
+  with a clean control each. It asserts that every case it planned actually ran,
+  and refuses when a rule list it derives cases from is empty.
+- **A repository leak sweep** over the working tree and the history, with **no
+  file skipped**, which refuses (exit 2) rather than passing when there is
+  nothing to read: no tracked files, no commits, no blobs, an empty ruleset, or
+  a rule whose window can no longer match what it is for. The names it looks for
+  are salted hashes rather than text, so the rules file carries no secret and
+  needs no exemption - the previous arrangement published the list it was
+  protecting and then skipped the file it was in. A name is looked for across
+  every separator, at camel-case boundaries, inside an unbroken run of letters
+  and digits, and in the file path as well as in the contents. Findings print a
+  hash prefix, a length and a location, never the value - a host, a dependency
+  spec and a path included, and in the findings themselves rather than only in
+  the listing above them: every location a finding carries is built in one
+  place, so there is no second printing site to remember. The self-test asserts
+  the absence as well as the presence - a case that catches what it was given
+  and prints it while doing so fails.
+- **Two rules now govern what may go on the private-name list, and they are in
+  `scripts/rules.json` next to the list rather than in a review thread.** They
+  fail in opposite directions. An entry must not be a substring of text this
+  repository legitimately prints, because such an entry can never be satisfied
+  and the only ways out are deleting it or weakening the scanner. And nothing
+  whose harm *is* the confirmation of a guess may ever be added - a credential,
+  a key or token, a password, a session, subscription or contract identifier, a
+  certificate serial, a hostname that grants access, personal data - because
+  the list is public and it answers questions. A table name confirmed is a fact
+  about a schema a stranger cannot reach; an identifier confirmed *is* the
+  identifier. Nothing on the list is from that class, checked rather than
+  assumed.
+- **What the hashes do is now a measured number rather than an impression.**
+  A wordlist built from the platform's own files recovers **all** of them; a
+  wordlist of ordinary English and technical vocabulary recovers **none** over
+  236,132 candidates. The file used to say "most of them", which understated
+  the property the arrangement depends on. The hashing is a lint aid, not a
+  store, and that sentence is now at the two places where somebody is told how
+  to add an entry, rather than four paragraphs away in the rationale.
+- **Two entries changed under the first of those rules**: one removed (8
+  characters) and one replaced (7 characters out, 10 in), with the rule, the
+  lengths and the declared narrowing recorded and nothing else. A name of
+  several segments is stored **glued** from now on: the scanner offers every
+  window both glued and underscore-joined, so the glued form is found in all
+  ten placements measured - including inside a run of letters with no boundary
+  in it, the shape a name takes in a minified bundle - while the
+  underscore-joined form is found in nine. `blindSpots()` said "with none at
+  all" while the entry was stored the other way, and a check that overstates
+  its own coverage is worse than one that understates it; it now states the
+  condition it actually depends on.
+- **The worked example for that spelling rule can now be reproduced.** The pair
+  it used was shorter than `minTokenLength`, so a reader who tried it literally
+  matched nothing and concluded the rule was broken - and it is printed on every
+  run, in four places. Both spellings of the replacement are inside the declared
+  window. `_tokenLength` now says what those two numbers are: **the scanner's
+  bounds, not a description of the entries, and not to be adjusted to fit them.**
+  The decoders size themselves from the lower bound, so trimming the range to
+  match whatever is on the list would stop shorter encoded forms from being
+  looked at *and* sharpen a published range, in one edit that would feel like
+  housekeeping. An entry outside the window means widening the window.
+- **Earlier wordings of those notes, in this file and in `scripts/rules.json`,
+  said what the changed entries were *about*.** Together those descriptions
+  narrowed the guess for a live entry further than the hashes do, which is the
+  caption failure the numbers list refuses on the facing page. The wording is
+  corrected going forward and no more than that is claimed: the earlier text is
+  in this repository's history and in the pull request that carried it, and
+  editing a published file does not unpublish it - the same reasoning
+  `CONTRIBUTING.md` gives for not squash-merging. The rule from here on is to
+  record the rule, the lengths and the narrowing, and never the subject.
+- **Two more module-scope ruleset loads are guarded.** The gate's self-test and
+  the rule printer both died with an uncaught exception on a malformed or
+  missing `rules.json` - the self-test with exit 1 where its own header defines
+  2. Each leg loads the file for itself, so one guard cannot cover another.
+- **The publish gate cannot die of its own ruleset any more.** Loading
+  `rules.json` ran outside every guard, so an unreadable or malformed file
+  killed the gate with an uncaught exception - exit 1, the code that means
+  *findings*, and a stack trace carrying absolute paths - for a condition its
+  own contract defines as exit 2. It now refuses like the sweep does, and a
+  ruleset file that is not JSON is a case in the self-test on all three legs.
+- **The tarball that is checked is the tarball that is published.** The publish
+  workflow packed once for the gate and again for `npm publish`; it now packs
+  once and hands that exact file to both.
+- **The endpoint check in CI fails when it reads nothing.** It grepped `test/`
+  and passed on no hits, so an empty or renamed directory reported success; it
+  now asserts that the one legitimate occurrence is there before judging it.
+- **[SOURCES.md](SOURCES.md) - where every answer comes from**, and it ships in
+  the tarball beside NOTICE rather than living only on the web page. One entry
+  per source: who publishes it, what it covers, the publisher's own rhythm, the
+  licence with the operative sentence quoted and the date it was read, and the
+  **exact attribution line** a recipient has to reproduce. Two obligations that
+  bind the *reader* are stated before the catalogue rather than linked from it:
+  MTS-K fuel prices are consumer information only and may not be redistributed
+  in any form, aggregates included, and DELFI public-transport realtime is
+  CC BY-SA 4.0, so anything derived from it stays share-alike. The page says
+  which sources do **not** answer today - fuel coverage is a watch list and not
+  the country, station lift and escalator status is not available on the public
+  service yet - and it names the three cases where a publisher's terms are
+  unknown or unreadable instead of rounding them up to "open data".
+- **The leak sweep now distinguishes a data provider from the platform, in
+  writing.** It did not before, and the distinction was carried by the
+  private-name list rather than by a rule: the sweep refused the page above,
+  in eleven places in it and one in the rules file itself. **Two entries were
+  removed under the first list rule** (10 and 12 characters), and **the two had
+  different reasons**, which is worth separating because the stronger one does
+  not cover both. The 12-character spelling is **compelled**: a licence
+  requires that source to be named by a link, and the link's host contains it.
+  The 10-character one is not compelled by any licence - the attribution
+  conditions require the creator, the notices and a supplied URI, and none of
+  them requires naming an intermediary - it is simply a spelling **our own
+  server already broadcasts** in the attribution line it hands to every user
+  who receives such an answer, so a page that quotes that line cannot avoid it
+  and the rule could be satisfied only by never writing the page. The
+  alternative was real and was not taken: the server's own line could have been
+  narrowed so it never named the intermediary. It was not, because that line is
+  the server's to decide rather than a lint rule's, and because naming the route
+  data reached us by is provenance a reader checking a claim uses. That is a
+  product decision, and it is recorded as one rather than as law. Rule 2 was
+  applied to both before they went - neither is a credential, an identifier or a
+  host that grants access. What replaces them is a boundary between a **name**
+  and a **route**: a publisher or an intermediary may be named wherever the
+  server's own public attribution names it, while a fetch endpoint, an API path,
+  a per-offer deep link or a subscription identifier may not appear at all -
+  which is why the access point is named in words and its host is on no
+  allow-list. The host allow-list gains a second group on the same test: the
+  page that publishes a source's terms, the licence text it invokes, or a URL a
+  licence compels us to print, and nothing that merely looks relevant.
+- **Merged with a merge commit, never a squash**, and
+  [CONTRIBUTING.md](CONTRIBUTING.md) says why at length: the history sweep's
+  accepted residue is keyed by blob, those blobs live only in intermediate
+  commits, and a squash makes them unreachable from `main` - which would turn
+  the check red on `main` for everybody, for something no contributor did.
+
+[0.0.9]: https://github.com/mavrovde/viafrei-bridge/releases/tag/v0.0.9

package/LICENSE

@@ -0,0 +1,218 @@
+                                 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 ViaFrei
+
+   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.
+
+
+
+-------------------------------------------------------------------------------
+ADDENDUM — what this licence does not cover
+
+The Apache License above covers THIS CODE ONLY: the stdio-to-Streamable-HTTP
+bridge in this repository.
+
+Data obtained through the ViaFrei MCP server keeps its own provider licence and
+is not relicensed by anything here. Several of those licences are share-alike
+(DELFI public-transport data is CC BY-SA 4.0) or purpose-limited (MTS-K fuel
+prices are consumer information only, with no redistribution in any form,
+aggregates included).
+
+Each tool result carries its own attribution line, and the full register is
+published by the server at the resource `viafrei://attribution`. See NOTICE.

package/NOTICE

@@ -0,0 +1,32 @@
+ViaFrei bridge
+Copyright 2026 ViaFrei
+
+This product is licensed under the Apache License, Version 2.0 (see LICENSE).
+
+THE LICENCE ABOVE COVERS THIS CODE ONLY.
+
+Data obtained *through* the ViaFrei MCP server is not ours to relicense and
+keeps its provider's own terms. Those terms travel with the answer, not with
+this package, and several of them are share-alike or purpose-limited. In
+particular:
+
+  - DELFI public-transport data is CC BY-SA 4.0. Share-alike: anything derived
+    from it inherits the obligation, and it must not be blended into a result
+    carrying a different licence.
+  - MTS-K fuel prices (Tankerkönig) are consumer information only. No
+    redistribution in any form, aggregates and derived tables included.
+  - Address results are derived from OpenStreetMap under the ODbL 1.0. The
+    share-alike is on the database rather than on the sentence, and our offer
+    under section 4.6 stands: ask and you get the extract and our alterations
+    to it under the same licence.
+  - Autobahn GmbH, BKG, DWD, Deutsche Bahn, GeoNames and the AFIR charging
+    feeds each carry their own licence and attribution string.
+
+Every tool result from the server carries its own attribution line, and the
+server exposes the full register at the resource `viafrei://attribution`. Show
+the attribution line to the person reading the answer. If you are building on
+top of this bridge, read that resource before you decide what you may do with
+what comes back.
+
+SOURCES.md in this package lists every source, its publisher, its licence and
+the attribution line it requires, in full.