provael 0.1.0__tar.gz

provael-0.1.0/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Security vulnerability (report privately)
+    url: https://github.com/provael/provael/security/advisories/new
+    about: Please report security issues privately via a GitHub security advisory — see SECURITY.md, not a public issue.

provael-0.1.0/.github/ISSUE_TEMPLATE/leaderboard-submission.yml

@@ -0,0 +1,49 @@
+name: Leaderboard submission
+description: Submit a VLA policy's robustness result to the Provael leaderboard
+title: "[leaderboard] <policy> on <suite>"
+labels: ["leaderboard"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for contributing a result! The fastest path is a **pull request** adding
+        `results/<name>/report.json` — see
+        [CONTRIBUTING-leaderboard.md](../blob/main/CONTRIBUTING-leaderboard.md). Use this
+        issue if you'd like help, can't open a PR, or want to propose a checkpoint to add.
+  - type: input
+    id: policy
+    attributes:
+      label: Policy / checkpoint
+      placeholder: "e.g. HuggingFaceVLA/smolvla_libero"
+    validations:
+      required: true
+  - type: input
+    id: suite
+    attributes:
+      label: Suite + task(s)
+      placeholder: "e.g. libero_object/0,1,2"
+    validations:
+      required: true
+  - type: input
+    id: setup
+    attributes:
+      label: Seeds / horizon / hardware
+      placeholder: "e.g. 10 seeds, horizon 280, RTX 4090, MUJOCO_GL=osmesa"
+    validations:
+      required: true
+  - type: textarea
+    id: report
+    attributes:
+      label: report.json (paste or link)
+      description: Paste the `report.json` produced by `provael attack`, or link the run.
+    validations:
+      required: true
+  - type: checkboxes
+    id: checks
+    attributes:
+      label: Checklist
+      options:
+        - label: "Produced via `provael attack` and includes a `none` baseline"
+          required: true
+        - label: "I understand results are seeded/reproducible and may be re-run"
+          required: true

provael-0.1.0/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,20 @@
+## Summary
+
+<!-- What does this change and why? -->
+
+## Test plan
+
+<!-- How did you verify it? For code changes: -->
+<!-- `uv run ruff check . && uv run mypy src && uv run pytest -q` -->
+
+---
+
+### Leaderboard submission? (delete this section if N/A)
+
+- [ ] Adds `results/<name>/report.json` produced by `provael attack` (with a `none` baseline)
+- [ ] `python scripts/validate_submission.py` passes locally
+- [ ] Reproducible: checkpoint, suite/task(s), seeds, horizon, and hardware noted below
+
+<!-- policy/checkpoint:
+     suite/tasks:
+     seeds / horizon / hardware: -->

provael-0.1.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 (PROVAEL_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

provael-0.1.0/.github/workflows/leaderboard-submission.yml

@@ -0,0 +1,28 @@
+name: Leaderboard submission
+
+# Validates external leaderboard submissions on PRs that add/change results/**.
+# CPU-only — never installs lerobot. Confirms each report.json is a valid, internally
+# consistent RunReport and that the leaderboard still builds from results/*.
+
+on:
+  pull_request:
+    paths: ["results/**"]
+
+permissions: {}  # read-only; least privilege
+
+jobs:
+  validate:
+    name: Validate submission + rebuild leaderboard
+    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: Install (locked, CPU core only)
+        run: uv sync --locked
+      - name: Validate submitted report(s)
+        run: uv run python scripts/validate_submission.py 'results/*'
+      - name: Leaderboard builds cleanly
+        run: uv run provael leaderboard build --runs 'results/*' --out "${RUNNER_TEMP}/lb"

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

@@ -0,0 +1,96 @@
+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 : provael
+#        Owner             : provael
+#        Repository name   : provael
+#        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
+        with:
+          skip-existing: true  # don't hard-fail if a re-run hits an already-uploaded version
+        # 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

provael-0.1.0/.gitignore

@@ -0,0 +1,53 @@
+# 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/
+
+# private strategy/market docs — never publish
+/vla-redteam-*.md

provael-0.1.0/CHANGELOG.md

@@ -0,0 +1,51 @@
+# 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-27
+
+Initial **Provael** release. Provael is the open-source red-team & assurance layer for
+physical AI — a CPU-first, model-agnostic harness that perturbs the instructions and
+observations a Vision-Language-Action (VLA) robot policy receives in simulation and reports
+an Attack Success Rate (ASR).
+
+> **Renamed from `vla-redteam` / `robopwn`.** The same engine and full git history, under a
+> new name, CLI (`provael`), and home (github.com/provael/provael). It was previously
+> published on PyPI as `vla-redteam` (0.1.0–0.2.2); the env-var gate is now
+> `PROVAEL_INTEGRATION`. Behavior is unchanged — the deterministic stub run still reports
+> ASR 67.1% (47/70), byte-identical.
+
+### Included
+- **CPU-first deterministic core** — `StubPolicy` + `StubSuite` give exact, byte-reproducible
+  ASRs with no GPU or model download; strict typing, `py.typed`, 100 tests.
+- **Three templated attack families** (`instruction`, `visual`, `injection`) + a `none`
+  baseline; ASR with per-attack / per-task breakdowns and seeded mean ± std for real policies.
+- **Real SmolVLA × LIBERO path** behind the `[lerobot]` extra + `PROVAEL_INTEGRATION=1`,
+  replicating LeRobot's verified evaluator rollout; first real result on `libero_object/0`
+  (instruction attacks 60–100% vs a 0% benign baseline; visual/injection 0% — honest null).
+- **Per-task calibrated keep-out zones** scaffold (`suites/keepout_zones.py` +
+  `scripts/calibrate_zones.py`) toward a calibrated hazard rate.
+- **Leaderboard** — deterministic `(policy × suite × family) → ASR` table, a Gradio Space, and
+  a public submission flow (validator + CI on `results/**`).
+- **CLI `provael`** — `attack`, `report`, `leaderboard build`, `list-policies`,
+  `list-attacks`, `version`; actionable errors (exit code 2), never a traceback.
+- Apache-2.0; OIDC trusted-publishing release pipeline; strict `ruff` + `mypy` gate in CI.
+
+### Honest scope
+Attacks are templated (not gradient/optimization-based); only the instruction family
+transfers to real SmolVLA so far; one policy + one suite shipped; the headline result uses a
+single task with a default, uncalibrated keep-out predicate. See the README's
+"Scope and honest limitations."
+
+### Roadmap
+- **v0.2.0** — SARIF output (`provael report --format sarif`) for GitHub code scanning; a
+  reusable `provael/provael-action` CI gate; an Embodied-AI Top-10 risk mapping; per-task
+  keep-out-zone calibration.
+- **later** — optimized (gradient/search) attacks; a second policy/suite backend.
+
+> Detailed pre-rebrand history (the `vla-redteam` 0.2.x line) is preserved in the git log and
+> the prior PyPI releases.
+
+[0.1.0]: https://github.com/provael/provael/releases/tag/v0.1.0

provael-0.1.0/CONTRIBUTING-leaderboard.md

@@ -0,0 +1,48 @@
+# Submitting to the Provael leaderboard
+
+The [leaderboard](https://huggingface.co/spaces/Sattyam/provael-leaderboard) aggregates
+real `(policy × suite × family) → ASR` results. Anyone can add a result via a pull request —
+CI validates it automatically.
+
+## How to submit (pull request)
+
+1. **Run an attack** on your policy, including the `none` baseline (so we can read *lift*):
+
+   ```bash
+   pip install 'provael[lerobot]' 'lerobot[libero]==0.5.1'
+   export MUJOCO_GL=osmesa PYOPENGL_PLATFORM=osmesa   # headless rendering
+   provael attack --policy smolvla --suite libero --model <your-checkpoint> \
+       --attacks none,instruction,visual,injection --seeds 10 --horizon 280 --seed 0 \
+       --out results/<your-name>            # writes results/<your-name>/report.json
+   ```
+
+2. **Validate locally** (same check CI runs):
+
+   ```bash
+   python scripts/validate_submission.py 'results/*'
+   ```
+
+3. **Open a PR** adding `results/<your-name>/report.json`. The **Leaderboard submission**
+   workflow validates the report and confirms the leaderboard still builds. In the PR
+   description, note the checkpoint, suite/task(s), seeds, horizon, and hardware.
+
+4. On merge, a maintainer rebuilds the published board
+   (`provael leaderboard build --runs 'results/*' --out leaderboard/results`) and the Space
+   updates. (`is_demo` clears automatically once any non-stub result is present.)
+
+## What the validator checks
+
+- The file parses as a `RunReport`.
+- ASR ∈ [0, 1]; `successes` ∈ [0, `attempts`].
+- `attempts` equals the number of **applicable** episodes (not-applicable attacks are
+  excluded from the denominator, never faked).
+- `successes` matches the applicable successes in the per-episode results.
+- Every result has an `attack` and `family`.
+
+## Norms (please)
+
+- **Reproducible & seeded.** Report the exact checkpoint, suite/tasks, seeds, and horizon.
+- **Honest scope.** If you used a custom keep-out predicate or calibrated zones, say so.
+- **No fabricated numbers.** Results may be independently re-run.
+
+Questions or can't open a PR? Use the **Leaderboard submission** issue template.

provael-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,63 @@
+# Contributing to provael
+
+Thanks for your interest in improving **provael** (Provael). This is a defensive,
+sim-only security-research tool — please read [SAFETY.md](SAFETY.md) first.
+
+## Ground rules
+
+- **CPU-first.** The entire core runs and is tested on a plain CPU with **no GPU and no
+  model/dataset download**. Real policies (SmolVLA via LeRobot) and the LIBERO simulator
+  live behind the optional `[lerobot]` extra and a `PROVAEL_INTEGRATION=1` gate. **CI never
+  installs `lerobot`** — keep it that way.
+- **Verify, don't fabricate.** Numbers in the README/CHANGELOG must come from a real run.
+  When a third-party API is involved, read/introspect the installed source rather than
+  guessing; if something can't be verified (no GPU/sim), say so and ship a clearly-skipped
+  gated test instead of a guess.
+- **Determinism.** The stub policy/suite are byte-deterministic; real policies are seeded
+  but model-stochastic (reported as mean ± per-seed std). Don't put wall-clock into
+  `report.json`.
+
+## Dev setup
+
+```bash
+# uv (recommended): https://docs.astral.sh/uv/
+uv sync                      # core + dev tools (no GPU stack)
+uv run provael --help
+```
+
+## The gate (must be green before you push)
+
+```bash
+uv run ruff check .          # lint + import order
+uv run mypy src              # strict type-check
+uv run pytest -q             # tests (GPU/LIBERO tests auto-skip without the extra)
+```
+
+The optional, GPU-gated integration tests:
+
+```bash
+pip install 'provael[lerobot]' 'lerobot[libero]==0.5.1'
+PROVAEL_INTEGRATION=1 pytest tests/test_lerobot_adapter.py tests/test_libero_adapter.py -q
+```
+
+## Conventions
+
+- **Python 3.12+**, type hints on all signatures, pydantic v2 for data models.
+- **Commits**: imperative, conventional-style prefixes (`feat:`, `fix:`, `docs:`,
+  `test:`, `chore:`), concise subject (< 72 chars), body for context.
+- **Architecture**: ports-and-adapters — new policies subclass `PolicyAdapter`, new suites
+  `SuiteAdapter`, new attacks `Attack`; register them in the relevant registry and add a
+  CPU test (use the stub) plus a gated test if a GPU/sim is required.
+- Keep optional dependencies imported **only inside methods**, never at module scope.
+
+## Pull requests
+
+1. Branch (`feature/…`, `fix/…`), make the change, keep the gate green.
+2. Add/extend tests; for new attacks, include the deterministic stub ASR.
+3. Update `CHANGELOG.md` (`[Unreleased]`) and any affected docs.
+4. Open the PR with a **Summary** and a **Test Plan**.
+
+## Reporting bugs / requesting features
+
+Open a GitHub issue (templates provided). For security vulnerabilities, see
+[SECURITY.md](SECURITY.md) — please do **not** open a public issue for those.

provael-0.1.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.