unshackle 0.1.0__tar.gz

unshackle-0.1.0/.github/ISSUE_TEMPLATE/fixture-submission.yml

@@ -0,0 +1,28 @@
+name: Fixture submission
+description: Share an anonymized export so we can test against real-world definitions.
+labels: [fixture]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you! Real exports are the best way to make translations reliable.
+        **Before attaching anything,** remove names, emails, hostnames, IDs and anything confidential.
+  - type: dropdown
+    id: tool
+    attributes:
+      label: Source tool
+      options: [Looker, Tableau, Power BI, Lightdash, Omni, Hex, Sigma, ThoughtSpot, Other]
+    validations:
+      required: true
+  - type: textarea
+    id: notes
+    attributes:
+      label: What's interesting about it
+      description: Features it uses (e.g. LOD expressions, Liquid, row-level security) and anything unshackle gets wrong today.
+  - type: checkboxes
+    id: consent
+    attributes:
+      label: Permission
+      options:
+        - label: I have the right to share this, and it's been anonymized. It can be published under Apache 2.0.
+          required: true

unshackle-0.1.0/.github/ISSUE_TEMPLATE/new-source.yml

@@ -0,0 +1,29 @@
+name: New source
+description: Propose support for a BI tool unshackle doesn't read yet.
+labels: [new source]
+body:
+  - type: input
+    id: tool
+    attributes:
+      label: BI tool
+    validations:
+      required: true
+  - type: textarea
+    id: access
+    attributes:
+      label: How can definitions be exported?
+      description: API docs, a manual export (files you can download), or a Git integration. Links help.
+    validations:
+      required: true
+  - type: textarea
+    id: scope
+    attributes:
+      label: What matters most to you
+      description: Metrics, dashboards, saved queries, permissions? Which would you want first?
+  - type: checkboxes
+    id: help
+    attributes:
+      label: Can you help?
+      options:
+        - label: I can share an anonymized export as a test fixture
+        - label: I'd like to build the source myself

unshackle-0.1.0/.github/ISSUE_TEMPLATE/translation-bug.yml

@@ -0,0 +1,23 @@
+name: Translation bug
+description: Something was translated wrong, or a number doesn't match the BI tool.
+labels: [bug]
+body:
+  - type: dropdown
+    id: tool
+    attributes:
+      label: Source tool
+      options: [Looker, Tableau, Power BI, Lightdash, Omni, Hex, Sigma, ThoughtSpot, Other]
+    validations:
+      required: true
+  - type: input
+    id: versions
+    attributes:
+      label: Versions
+      description: unshackle version (`unshackle --version`) and the BI tool version, if you know it.
+  - type: textarea
+    id: what
+    attributes:
+      label: What happened
+      description: The original definition, what unshackle produced, and what you expected. Remove anything confidential.
+    validations:
+      required: true

unshackle-0.1.0/.github/pull_request_template.md

@@ -0,0 +1,7 @@
+## What and why
+
+## How I tested it
+
+- [ ] `pytest` passes
+- [ ] `./examples/tableau-demo/run.sh` passes
+- [ ] Commits are signed off (`git commit -s`)

unshackle-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,21 @@
+name: ci
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python: ["3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v6
+      - run: uv venv --python ${{ matrix.python }} && uv pip install -e ".[dev]"
+      - run: uv venv /tmp/dbt && uv pip install --python /tmp/dbt/bin/python "dbt-core>=1.9" dbt-duckdb
+      - run: .venv/bin/pytest -q
+        env:
+          UNSHACKLE_DBT: /tmp/dbt/bin/dbt
+      - run: ./examples/tableau-demo/run.sh /tmp/acme

unshackle-0.1.0/.github/workflows/dco.yml

@@ -0,0 +1,20 @@
+name: dco
+on: pull_request
+
+jobs:
+  signoff:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - name: Check every commit is signed off
+        run: |
+          missing=0
+          for sha in $(git rev-list --no-merges ${{ github.event.pull_request.base.sha }}..${{ github.event.pull_request.head.sha }}); do
+            if ! git log -1 --format=%B "$sha" | grep -q '^Signed-off-by: '; then
+              echo "::error::Commit $sha is missing a Signed-off-by line. See CONTRIBUTING.md."
+              missing=1
+            fi
+          done
+          exit $missing

unshackle-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,33 @@
+name: release
+on:
+  push:
+    tags: ["v*"]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v6
+      - name: Check the tag matches the package version
+        run: |
+          version=$(grep -m1 '^version = ' pyproject.toml | cut -d'"' -f2)
+          test "v$version" = "${GITHUB_REF_NAME}" || { echo "::error::tag ${GITHUB_REF_NAME} != version $version"; exit 1; }
+      - run: uv build
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write   # PyPI trusted publishing; no API token is stored
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1

unshackle-0.1.0/.github/workflows/site.yml

@@ -0,0 +1,32 @@
+name: site
+on:
+  push:
+    branches: [main]
+    paths: ["site/**", "assets/banner.svg", ".github/workflows/site.yml"]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: pages
+  cancel-in-progress: true
+
+jobs:
+  deploy:
+    # Pages goes live with the repo; skip while it's private.
+    if: ${{ !github.event.repository.private }}
+    runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - uses: actions/checkout@v4
+      - run: mkdir _site && cp site/* assets/banner.svg _site/
+      - uses: actions/upload-pages-artifact@v3
+        with:
+          path: _site
+      - id: deployment
+        uses: actions/deploy-pages@v4

unshackle-0.1.0/.gitignore

@@ -0,0 +1,9 @@
+.venv/
+__pycache__/
+*.pyc
+.pytest_cache/
+*.egg-info/
+dist/
+.env
+.unshackle/
+.user.yml

unshackle-0.1.0/AGENTS.md

@@ -0,0 +1,63 @@
+# Agent instructions
+
+This repo is `unshackle`: it migrates BI tools into open formats in a Git repo.
+There are two ways you might be here.
+
+## Migrating a customer's BI tool
+
+You're running inside the customer's repo with `unshackle` installed. Load
+`skills/migrate/SKILL.md` and follow it. The other skills:
+
+| Skill | Use it for |
+| --- | --- |
+| `skills/source-<tool>/SKILL.md` | Access, what's automatic, tool-specific translation (looker, lightdash, omni, hex, sigma, thoughtspot, powerbi, tableau, metabase, superset, redash, quicksight, qlik) |
+| `skills/translate-metrics/SKILL.md` | Calculations -> Apache Ossie (plus MetricFlow in dbt projects) or SQL models |
+| `skills/translate-dashboards/SKILL.md` | Finishing notebook tiles and Altair charts |
+| `skills/translate-permissions/SKILL.md` | BI security -> Cedar + row filters |
+| `skills/verify/SKILL.md` | Parity checks against the source tool |
+
+Folders in the customer's repo (each appears only once something is written to it):
+
+| Folder | Purpose |
+| --- | --- |
+| `semantic/` | Metrics and semantic models (Apache Ossie; MetricFlow too in dbt projects) |
+| `catalog/` | Table and column descriptions, one YAML file per table |
+| `knowledge/` | Business context in Markdown |
+| `queries/` | Saved SQL or Python queries; `queries/models/` holds SQL models |
+| `notebooks/` | Dashboards as Jupyter notebooks (SQL + Altair) |
+| `policies/` | Cedar policies and SQL row filters |
+| `evals/` | Passing parity cases, written by `unshackle verify` |
+| `data/` | Data copied out of the tool with `--with-data` (git-ignored) |
+| `migration/` | unshackle's own area: raw exports, report, lock, skills, parity cases |
+
+Rules: credentials stay in the environment or the repo's git-ignored `.env`, never in
+tracked files. Work on a branch and
+open a pull request. Never delete a `TODO(unshackle)` without resolving it.
+
+## Working on unshackle itself
+
+- Code: `src/unshackle/`. `ir.py` is the neutral model; `sources/<tool>.py` implement
+  `inventory`, `extract`, `parse` (see `sources/base.py`); `target/` writes the structure.
+- `parse()` never touches the network and is tested from `tests/fixtures/<tool>/`.
+- Anything a parser can't translate faithfully keeps `source_expression` and sets `todo`.
+- Generated SQL divides with `1.0 * a / nullif(b, 0)`. Dashboards are Jupyter
+  notebooks (`target/notebooks.py`) with Altair charts; facets, layers and concatenation
+  are fine when the source chart needs them.
+- Run `uv pip install -e ".[dev]" && pytest` and `./examples/tableau-demo/run.sh`
+  before pushing.
+- Tests are offline: parsers run on saved exports in `tests/fixtures/`, and generated SQL runs
+  in DuckDB on the fictional Dunder Mifflin data (`tests/data/dunder_mifflin/`). Expected
+  numbers are computed in the test from the tool's documented semantics, not copied from a tool.
+- Fixtures and test data never contain real hostnames, site or tenant names, account ids,
+  emails or tokens. Replace them with `example.*` values before committing.
+
+### Workflow
+
+- Work is tracked in GitHub issues. One branch and one pull request per change; say which
+  issue it closes (`Closes #N`).
+- Sign off every commit (`git commit -s`; see `CONTRIBUTING.md`).
+- PR descriptions are plain and factual: what changed, how it was tested, what stays TODO.
+  Pull requests and issues written with a coding agent end with the line
+  `Assisted by Claude Code` (or the equivalent for your agent).
+- Changes that touch the same files as an open PR (`CHANGELOG.md`, `pyproject.toml` extras)
+  are rebased on `main` after that PR merges.

unshackle-0.1.0/CHANGELOG.md

@@ -0,0 +1,22 @@
+# Changelog
+
+## 0.1.0 (2026-10-27)
+
+First release.
+
+- **Sources (13):** Tableau, Power BI, Looker, Qlik Sense, Amazon QuickSight, Metabase, Lightdash, Apache Superset,
+  Redash, Omni, Hex, ThoughtSpot and Sigma, through their APIs (`unshackle migrate`), or from downloaded files
+  (`unshackle import`) for all but Metabase, Redash and Sigma.
+- **Outputs:** Apache Ossie semantic models and metrics; dashboards as Jupyter notebooks (SQL per tile, Altair
+  charts); SQL queries and models; Cedar policies and SQL row filters; table descriptions and Markdown knowledge.
+- **Nothing guessed:** what can't be translated faithfully stays a `TODO(unshackle)` with the original expression.
+  `migration/report.md` shows per dashboard how many tiles have SQL and what blocks the rest; `unshackle todo` lists
+  every item.
+- **Commands:** `check` (credentials, with `--prompt` to save them to `.env`), `migrate` (`init`, `inventory`,
+  `extract` and `build` in one go), `import`, `run` (execute the notebooks), `verify` (migrated numbers against the
+  source's; `verify --init tableau` writes the cases from Tableau's view data), `todo`, `status`, `report`.
+- **Data that lives only in Tableau** (extracts, Excel, CSV) can be copied to Parquet with `--with-data` and loaded
+  into a local DuckDB file the notebooks read. `.hyper` extracts need `pip install "unshackle[hyper]"`.
+- **Install:** `pip install unshackle` (or `uv tool install unshackle`).
+
+Changes before the first release are in the git history.

unshackle-0.1.0/CLAUDE.md

@@ -0,0 +1 @@
+@AGENTS.md

unshackle-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,13 @@
+# Code of conduct
+
+Be kind. Assume good intent. Disagree about code, not people.
+
+Not okay here: harassment, insults, personal attacks, sexual language or
+imagery, publishing someone's private information, or anything else you
+wouldn't do in front of a colleague.
+
+This applies in issues, pull requests, discussions and anywhere you
+represent the project.
+
+Maintainers can edit or remove comments and contributions, and warn or ban
+anyone who breaks these rules.

unshackle-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,79 @@
+# Contributing to unshackle
+
+Thanks for helping. unshackle gets definitions out of BI tools and into open
+formats in a Git repo. Most of the work is in two places: **sources** (reading a
+BI tool) and **targets** (writing open formats).
+
+## Set up
+
+```bash
+git clone https://github.com/Querio-App/unshackle
+cd unshackle
+uv venv && uv pip install -e ".[dev]"
+pytest
+./examples/tableau-demo/run.sh
+```
+
+Both must pass before you open a pull request.
+
+## How the code fits together
+
+| Path | What it does |
+| --- | --- |
+| `src/unshackle/ir.py` | The neutral model every source produces and every target reads |
+| `src/unshackle/sources/<tool>.py` | `inventory`, `extract` (network) and `parse` (offline); see `sources/base.py` |
+| `src/unshackle/target/` | Writers that turn the model into files |
+| `tests/fixtures/<tool>/` | Saved exports that `parse` is tested against |
+| `skills/` | Instructions for people and coding agents finishing a migration |
+
+Rules that keep output trustworthy:
+
+- `parse()` never touches the network. It's tested from `tests/fixtures/<tool>/`.
+- If something can't be translated faithfully, keep the original in
+  `source_expression` and set `todo`. A visible TODO beats a wrong number.
+- Generated SQL divides with `1.0 * a / nullif(b, 0)`.
+
+## Common contributions
+
+**Fix a translation.** Add the smallest fixture that shows the problem under
+`tests/fixtures/<tool>/`, write a failing test, then fix the parser.
+
+**Share a fixture.** Real exports are the most useful thing you can give us.
+Remove names, emails, hostnames and anything confidential first, and open a
+"Fixture submission" issue.
+
+**Add a source.** Open a "New source" issue first so we can agree on scope.
+Copy the shape of an existing source (`lightdash.py` is a good start): an
+`inventory`, an `extract` that saves raw files, and an offline `parse`.
+
+**Add a target.** Targets read the model in `ir.py` and write files. If you
+build a target for your own product, we're happy to take it.
+
+## Pull requests
+
+- Keep each pull request to one change, with a test.
+- Sign off every commit (see below).
+- Describe what changed and why. Mention which tool versions you tested against.
+
+## Sign your commits (DCO)
+
+We use the [Developer Certificate of Origin](https://developercertificate.org/)
+instead of a contributor license agreement. It says you have the right to submit
+your change under the project's license. Add a sign-off line to every commit:
+
+```bash
+git commit -s -m "Fix Tableau LOD parsing"
+```
+
+That adds `Signed-off-by: Your Name <you@example.com>`. CI checks for it. To fix
+commits you already made: `git rebase --signoff main`, then force-push your
+branch.
+
+## License
+
+By contributing, you agree that your contributions are licensed under the
+[Apache License 2.0](LICENSE).
+
+## Conduct
+
+Everyone taking part follows our [Code of Conduct](CODE_OF_CONDUCT.md).

unshackle-0.1.0/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.