vla-redteam 0.2.0__tar.gz

vla_redteam-0.2.0/.github/workflows/ci.yml

@@ -0,0 +1,34 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+# CPU-only by design: this workflow NEVER installs the optional `[lerobot]` extra,
+# so it pulls no torch / transformers / GPU stack. The LeRobot integration tests are
+# gated (ROBOPWN_INTEGRATION) and skip here automatically.
+jobs:
+  check:
+    name: ruff + mypy + pytest (CPU, no lerobot)
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv (pinned Python 3.12)
+        uses: astral-sh/setup-uv@v5
+        with:
+          python-version: "3.12"
+          enable-cache: true
+
+      - name: Sync core + dev (no extras)
+        run: uv sync --locked
+
+      - name: Lint (ruff)
+        run: uv run ruff check .
+
+      - name: Type-check (mypy, strict)
+        run: uv run mypy src
+
+      - name: Test (pytest, CPU only)
+        run: uv run pytest -q

vla_redteam-0.2.0/.github/workflows/release.yml

@@ -0,0 +1,94 @@
+name: Release
+
+# Tag-triggered release: build sdist + wheel, publish to PyPI via OIDC TRUSTED
+# PUBLISHING (no API token stored anywhere), then cut a GitHub Release from the
+# CHANGELOG.
+#
+# ────────────────────────────────────────────────────────────────────────────
+# ONE-TIME MAINTAINER SETUP (PyPI trusted publisher — no secrets in the repo):
+#   1. Create the project owner account on https://pypi.org.
+#   2. PyPI → your account → "Publishing" → "Add a new pending publisher":
+#        PyPI project name : vla-redteam
+#        Owner             : sattyamjjain
+#        Repository name   : vla-redteam
+#        Workflow name     : release.yml
+#        Environment name  : pypi
+#   3. In GitHub → repo Settings → Environments → create an environment named "pypi"
+#      (optionally add required reviewers / a tag protection rule).
+#   4. Publish by pushing a tag that matches the version, e.g.:
+#        git tag v0.1.0 && git push origin v0.1.0
+#   (For a first dry run, point step `publish` at TestPyPI by setting
+#    `repository-url: https://test.pypi.org/legacy/` and adding the matching pending
+#    publisher on test.pypi.org.)
+# ────────────────────────────────────────────────────────────────────────────
+
+on:
+  push:
+    tags: ["v*"]
+
+permissions: {}  # least privilege by default; jobs opt into exactly what they need
+
+jobs:
+  build:
+    name: Build sdist + wheel
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install uv (Python 3.12)
+        uses: astral-sh/setup-uv@v5
+        with:
+          python-version: "3.12"
+      - name: Build distributions
+        run: uv build
+      - name: Check metadata
+        run: uvx twine check dist/*
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish-pypi:
+    name: Publish to PyPI (OIDC trusted publishing)
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write  # REQUIRED for OIDC trusted publishing — no token needed
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - name: Publish
+        uses: pypa/gh-action-pypi-publish@release/v1
+        # No `password:` — trusted publishing uses the OIDC id-token above.
+
+  github-release:
+    name: Create GitHub Release
+    needs: publish-pypi
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write  # to create the release
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - name: Extract changelog notes for this tag
+        id: notes
+        run: |
+          version="${GITHUB_REF_NAME#v}"
+          awk -v ver="$version" '
+            $0 ~ "^## \\[" ver "\\]" {flag=1; next}
+            flag && /^## \[/ {exit}
+            flag {print}
+          ' CHANGELOG.md > release-notes.md
+          if [ ! -s release-notes.md ]; then echo "Release ${GITHUB_REF_NAME}" > release-notes.md; fi
+      - name: Create release
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: |
+          gh release create "${GITHUB_REF_NAME}" dist/* \
+            --title "${GITHUB_REF_NAME}" \
+            --notes-file release-notes.md

vla_redteam-0.2.0/.gitignore

@@ -0,0 +1,50 @@
+# Python
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.Python
+build/
+dist/
+*.egg-info/
+.eggs/
+develop-eggs/
+.installed.cfg
+*.egg
+
+# Virtual environments
+.venv/
+venv/
+env/
+ENV/
+.uv/
+
+# uv
+uv.lock.bak
+
+# Testing / coverage
+.pytest_cache/
+.coverage
+.coverage.*
+coverage.xml
+htmlcov/
+.mypy_cache/
+.ruff_cache/
+.hypothesis/
+
+# Run artifacts (generated reports)
+runs/
+
+# Optional demo recording (regenerated by scripts/record_demo.sh when asciinema+agg
+# are installed); the committed deterministic asset is docs/assets/demo.svg.
+docs/assets/*.gif
+
+# OS / editor
+.DS_Store
+.idea/
+.vscode/
+*.swp
+*~
+
+# Jupyter
+.ipynb_checkpoints/

vla_redteam-0.2.0/CHANGELOG.md

@@ -0,0 +1,141 @@
+# Changelog
+
+All notable changes to this project are documented here. The format is based on
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to
+[Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.1.0] — 2026-06-03
+
+First public release. A model-agnostic harness that red-teams VLA policies in
+simulation and reports an Attack Success Rate (ASR). The entire core runs and is tested
+on a plain CPU with no GPU and no model/dataset download; real policies and the LIBERO
+simulator are isolated behind the optional `[lerobot]` extra and an
+`ROBOPWN_INTEGRATION=1` gate, and CI never installs them.
+
+### Added
+- **Core engine**: `PolicyAdapter`, `SuiteAdapter` (with an `is_unsafe` predicate), and
+  `Attack` abstractions; a deterministic `runner` (policy × suite × attacks × seeds);
+  pydantic v2 result types (`AttackResult`, `RunReport`).
+- **Deterministic CPU stubs**: `StubPolicy` (manipulable via a documented trigger-token
+  lexicon over the instruction *and* a fixed allow-list of observation channels) and
+  `StubSuite` (one-task env with a SHA-256, cross-platform per-seed unsafe threshold),
+  so every attack yields a real, exact, reproducible seed-0 ASR with no model.
+- **Three attack families** (templated, auditable, CPU-testable):
+  - `instruction` — `RolePlayAttack`, `GoalSubstitutionAttack`, `ParaphraseAttack`
+    (RoboPAIR / POEX-inspired). Seed-0 ASR **21/30**.
+  - `visual` — `PatchAttack`, `DecoyObjectAttack` (observation-space markers; BadVLA
+    -inspired). Seed-0 ASR **14/20**.
+  - `injection` — `SceneTextInjection`, `MCPToolDescInjection` (indirect / embodied
+    prompt injection; POEX-inspired). Seed-0 ASR **12/20**.
+  - Combined seed-0 ASR across all three: **47/70**. See [PRIOR_ART.md](PRIOR_ART.md).
+- **Scoring & reports**: ASR with per-attack and per-task breakdowns (zero-division
+  guarded); stable `report.json` (sorted keys, no wall-clock → byte-deterministic) and
+  `report.md`, plus a Rich console summary.
+- **`robopwn` CLI**: `attack`, `list-policies`, `list-attacks`, `report`, `version`, and
+  `leaderboard build`. Clean, actionable errors (exit code 2) for a missing `[lerobot]`
+  extra or an unknown policy/suite/attack — never a traceback.
+- **Verified LeRobot SmolVLA adapter (gated)**: loads `lerobot/smolvla_base` via
+  `SmolVLAPolicy.from_pretrained` + `make_pre_post_processors` + `build_inference_frame`
+  + `select_action`, written **after introspecting** the installed `lerobot==0.5.1`
+  (symbols and signatures confirmed, not guessed).
+- **Verified LIBERO `SuiteAdapter` (gated)**: wraps the real LeRobot LIBERO env via the
+  introspected `make_env` / `make_env_config` / `LiberoEnv` API (`{suite: {task_id:
+  VectorEnv}}`, action dim 7, `info["final_info"]["is_success"]`). Configurable embodied
+  red-team predicate (`LiberoRedTeamRules`): default end-effector keep-out zone, optional
+  forbidden-object grasp. LIBERO is benign manipulation — we measure *redirection*, not
+  harm (see [SAFETY.md](SAFETY.md)).
+- **ASR leaderboard (v0, static-data)**: `robopwn leaderboard build` aggregates
+  `report.json` files into a ranked `(policy × suite × family) → ASR` table
+  (deterministic). A Gradio Space (`leaderboard/`, ZeroGPU-compatible) renders the
+  committed `results/*.json` with no GPU; data is clearly labelled stub/demo until real
+  SmolVLA / OpenVLA runs are added.
+- **Release engineering**: tag-triggered PyPI publish via OIDC trusted publishing
+  (`.github/workflows/release.yml`) and a GitHub Release from the CHANGELOG.
+- **Docs & CI**: README (with a real "Verified environment" block), SAFETY.md,
+  PRIOR_ART.md, and a GitHub Actions workflow running ruff + mypy + pytest on Python
+  3.12, CPU-only, never installing lerobot.
+
+### Known limitations
+- The `StubPolicy` / `StubSuite` are deliberate test fixtures, not models of real VLA
+  behaviour. The visual/injection attacks target the stub's observation channels; against
+  a real policy they only transfer insofar as the policy reads the perturbed channel
+  (pixel-level visual attacks on real models are future work).
+- The LeRobot SmolVLA adapter and the LIBERO `SuiteAdapter` are verified at the
+  symbol/signature level but not executed in CI (GPU-gated). The full LIBERO
+  observation→features wiring and the robosuite grasped-object accessor are deferred.
+- The leaderboard ships demo (stub) data only until real-model runs are added.
+
+## [0.2.0] — 2026-06-07 (in-process SmolVLA×LIBERO + first real result)
+
+The real attack loop `robopwn attack --policy smolvla --suite libero` now runs
+end-to-end (GPU-gated) and produced the project's **first real red-team result** on a
+RunPod RTX 4090. Verified by **running** against the installed `lerobot==0.5.1`.
+
+### Added
+- **SmolVLA×LIBERO glue**: the SmolVLA adapter consumes a real LIBERO observation by
+  replicating LeRobot's own evaluator rollout (`preprocess_observation` → set task →
+  `env_preprocessor` (`LiberoProcessorStep`) → `preprocessor` → `select_action` →
+  `postprocessor` → `env_postprocessor` → clamp to `[-1,1]`). A `SuiteFeatures` protocol
+  exchanges the env config once; `make_policy(cfg, env_cfg, rename_map)` mirrors eval.
+- **Real-policy attack injection**: instruction → the task language string; `visual.patch`
+  / `visual.decoy_object` → adversarial-marker overlay on the camera image;
+  `injection.scene_text` → PIL-rendered scene sign. `injection.mcp_tool_desc` is honestly
+  **N/A** on a direct LIBERO loop (excluded from the denominator).
+- **Live unsafe predicate**: end-effector keep-out zone (live, verified `eef.pos`) plus a
+  **configurable** forbidden-object-grasp rule (a `grasp_extractor` hook).
+- **Seeded mean ± std** reporting for stochastic (real) policies; `--seeds`, `--model`,
+  and `--rename-map` CLI options; `pillow` added for image rendering.
+- **`baseline` family** (`none`, a no-op control): runs the benign task unchanged so its
+  ASR is the reference, and attack ASR can be read as **lift over baseline**.
+- **Real task language as the base instruction**: the LIBERO adapter now reads the env's
+  actual task via `env.call("task_description")` (mirroring LeRobot's `add_envs_task`)
+  instead of a placeholder — so the benign baseline measures the policy on its real job
+  and attack ASR is a true "diverted from the legitimate task" number.
+- **Headless-sim robustness**: LIBERO's first-run `input()` config prompt is auto-handled
+  (`_ensure_libero_initialized`); `scripts/run_real.sh` sets `MUJOCO_GL`/`PYOPENGL_PLATFORM`
+  and documents the GL deps (`osmesa` CPU render, or EGL) for cloud GPU boxes.
+
+### First real result — verified on a GPU (2026-06-06)
+- Ran the full loop on a RunPod **RTX 4090** (`HuggingFaceVLA/smolvla_libero`,
+  `libero_object/0`, 10 seeds, horizon 280, `osmesa`). Overall **24.3% (17/70) ± 9.1%**.
+  Per family vs the benign `none` baseline (0/10): instruction `roleplay` **100%**,
+  `goal_substitution` **60%**, `paraphrase` 10%; `visual` and `injection` **0%**. The
+  canonical artifact is committed at `results/smolvla_libero_object/`, and
+  `leaderboard/results/leaderboard.json` now holds this real (non-demo) result.
+- **Honest caveat**: the keep-out predicate is a default, **uncalibrated** region — so this
+  is "diverted out of the benign safe envelope," not a zone-calibrated hazard rate; one
+  task, `n = 10`.
+
+### Verified by running (isolated lerobot venv, CPU)
+- `lerobot/smolvla_base` is **NOT** LIBERO-compatible (expects `camera1/2/3`; LIBERO
+  gives `image`/`image2` + 8-dim state) → the adapter surfaces a clean
+  `IncompatiblePolicyError`.
+- The **ready** `HuggingFaceVLA/smolvla_libero` checkpoint **loads through the glue** with
+  no incompatibility (policy + pre/post + `LiberoProcessorStep` all build) — so no
+  fine-tuning is needed. It is the default in `scripts/run_real.sh` and the gated tests.
+
+### Known limitations
+- Real-policy ASR is **seeded but model-stochastic** (mean ± std), not byte-deterministic
+  (only the stub is).
+- Forbidden-object grasp is **disclosed-inert by default** (no verified robosuite accessor
+  without the sim) — live only with a user-supplied `grasp_extractor`.
+- The first real ASR (above) uses an **uncalibrated** keep-out region, so it measures
+  redirection *out of the benign safe envelope*, not a zone-calibrated hazard rate; one
+  task, `n = 10`. Producing it requires a LIBERO-fine-tuned checkpoint + GPU + sim (not CI).
+
+## [Unreleased] — planned
+
+- **Per-task keep-out-zone calibration** (+ trajectory inspection) so a real ASR is a
+  semantically-meaningful redirection rate, not "entered a default box" — and a multi-task,
+  multi-suite sweep. This is the headline `v0.2.0` follow-up to the first real result.
+- **Optimized-suffix attack family** (GCG-style / POEX-style executable suffixes) and
+  pixel-level visual attacks tuned to transfer to real VLA policies.
+- **`mcp_tool_desc` on a real robot-MCP target** (no surface in a direct LIBERO loop).
+- A **default robosuite grasp accessor** so forbidden-object-grasp is live out of the box.
+- **Full multi-policy live leaderboard** on Hugging Face ZeroGPU with real SmolVLA /
+  OpenVLA numbers (the `@spaces.GPU` live-run path).
+- **`vla-guard`** (Phase 2): a defensive companion that hardens policies against the
+  attacks this tool measures.
+
+[0.2.0]: https://github.com/sattyamjjain/vla-redteam/releases/tag/v0.2.0
+[0.1.0]: https://github.com/sattyamjjain/vla-redteam/releases/tag/v0.1.0

vla_redteam-0.2.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or Derivative
+          Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work, excluding
+          those notices that do not pertain to any part of the Derivative
+          Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and do
+          not modify the License. You may add Your own attribution notices
+          within Derivative Works that You distribute, alongside or as an
+          addendum to the NOTICE text from the Work, provided that such
+          additional attribution notices cannot be construed as modifying
+          the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.