pytest-wardenbot 0.1.0__tar.gz

pytest_wardenbot-0.1.0/.gitignore

@@ -0,0 +1,67 @@
+# Python
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# Virtual environments
+.venv/
+venv/
+ENV/
+env/
+
+# Testing
+.pytest_cache/
+.coverage
+.coverage.*
+coverage.xml
+htmlcov/
+.tox/
+.nox/
+
+# Type checkers
+.mypy_cache/
+.pyright/
+.pyre/
+.ruff_cache/
+
+# IDEs
+.vscode/
+.idea/
+*.swp
+*.swo
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Secrets / local config
+.env
+.env.local
+*.local
+
+# Docs build
+site/
+_site/
+
+# Evaluation harness output (per-user, model-version-specific)
+scripts/evaluation/results/
+.pytest-eval-work/

pytest_wardenbot-0.1.0/BUILD-PLAN.md

@@ -0,0 +1,332 @@
+# pytest-wardenbot — Build Plan
+
+The plan for shipping `pytest-wardenbot` v0.1.0 to PyPI. ~7 sessions, each roughly half-day to full-day of focused work. Pulled forward from Wave 5 of the main WardenBot AI roadmap (see `~/Code/wardenbot/docs/implementation/14-execution-plan.md` §W5.13–W5.14) so the OSS funnel can seed dev mindshare before the managed Continuous Monitoring SaaS launches.
+
+## Context
+
+**What this is:** An open-source pytest plugin (Apache 2.0) that ships curated tests for chatbots and LLM apps. Developers `pip install pytest-wardenbot`, point it at their chatbot, run `pytest`, get back pass/fail with agent-ready remediation prompts for any failures.
+
+**Why now:** Three reasons.
+
+1. The plugin is genuinely standalone — no backend, no Stripe, no infra. It can ship before the managed SaaS does.
+2. Promptfoo (now OpenAI) and Giskard are racing toward our segment. A live PyPI package with stars and momentum plants a competitive flag.
+3. The attack corpus is something we need anyway. Building the plugin first means the corpus gets curated and battle-tested by real users before paid customers depend on it.
+
+**What this is NOT:**
+- Not the managed SaaS (that's Wave 6 of the main roadmap).
+- Not a sales tool with a "buy now" CTA (until the SaaS exists, the CTA points to the [intake form](https://wardenbot.ai/intake/)).
+- Not RAMPART-based (see §RAMPART below).
+- Not a way to call our hosted API (Sentry-tier customers get that via a separate authenticated mode in v0.3+).
+
+**Commitments we're making:**
+- Apache 2.0 license, forever.
+- Semver. No breaking changes within a major version.
+- No telemetry by default. Ever.
+- No bait-and-switch CTAs. The plugin's value proposition stands alone.
+- ~10–20% of one engineer's time ongoing — the plugin is a marketing budget line, not a revenue line.
+
+---
+
+## RAMPART decision: defer to v0.2
+
+The user asked specifically about including RAMPART. Decision: **defer to v0.2**. Reasoning:
+
+| Concern | Detail |
+|---|---|
+| **Alpha software** | RAMPART v0.1.0 released 2026-05-19. Microsoft AI Red Team, 4 maintainers. APIs explicitly subject to change. Pinning to an alpha dependency in a *stable* OSS release of our own would be a chronic source of breakage. |
+| **Agentic-only relevance** | RAMPART models XPIA (Cross-Prompt Injection Attack) — planting malicious instructions in data an agent reads, then triggering. The verdict logic returns UNDETERMINED for pure chatbots without tool calls. Our v0.1 users mostly have pure chatbots. |
+| **Hard dependency conflict** | RAMPART pins `pyrit==0.13.0`. That collides with anyone else holding PyRIT. Bad neighbor for a general-purpose pytest plugin. |
+| **No built-in chatbot adapters** | RAMPART ships zero adapters for OpenAI / Anthropic / LangChain / MCP / HTTP. We'd write them ourselves. Worth doing, but not before v0.1 ships. |
+
+**v0.2 path:** ship RAMPART as an optional extras install — `pip install pytest-wardenbot[agentic]` — gated to users who declare their bot has tools. The `AttackRunner` adapter pattern in v0.1 makes this drop-in (we just register a `RampartAttackRunner` alongside the deterministic / DeepEval-judge runners).
+
+Architecture decision: **v0.1 ships the adapter abstraction even though only one or two runners use it.** The cost is a Protocol class and a registry; the benefit is RAMPART (and any future runners) drop in without refactor.
+
+---
+
+## v0.1 scope
+
+**Tests we ship in v0.1** (target: 15 deterministic + 5 optional LLM-judge):
+
+| Category | Count | Grading | Requires API key? |
+|---|---|---|---|
+| Prompt-injection probes (regex on bad output) | 5 | deterministic | no |
+| System-prompt leak elicitation (substring on canary) | 3 | deterministic | no |
+| Refusal-bypass patterns (regex on disallowed-content tokens) | 3 | deterministic | no |
+| Business-truth assertion helpers (numeric / exact / substring match) | 2 (helpers; user-configured) | deterministic | no |
+| Off-topic deflection (substring on refusal markers) | 2 | deterministic | no |
+| Optional: semantic-equivalence checks via DeepEval | 5 | LLM judge | user's API key |
+
+The 15-deterministic-test floor matters: a new user runs `pytest` and sees 15 tests run in under 30 seconds against their bot with zero API spend. That's the install-to-first-green-test path that converts.
+
+**Chatbot adapters in v0.1:**
+- `HTTPChatbotAdapter` — generic HTTP POST with configurable auth (bearer / api-key header / custom header)
+- `OpenAIChatAdapter` — OpenAI Chat Completions API (optional extra: `pip install pytest-wardenbot[openai]`)
+- `AnthropicMessagesAdapter` — Anthropic Messages API (optional extra: `pip install pytest-wardenbot[anthropic]`)
+
+LangChain, MCP, OpenAI Assistants, Slack/Teams/Discord adapters: v0.2+.
+
+**Tech stack:**
+- Python 3.11+ (matches RAMPART; modern enough for `Protocol` + `Self` types).
+- `pytest >= 8` as the core runtime.
+- `pydantic >= 2` for adapter / response models.
+- `httpx` for HTTP transport.
+- `pytest-asyncio` for async-fixture tests.
+- Optional: `openai`, `anthropic`, `deepeval` — extras only.
+
+**Package structure:**
+
+```
+pytest-wardenbot/
+├── README.md
+├── LICENSE.md                  # Apache 2.0 (already in place)
+├── BUILD-PLAN.md               # this doc
+├── pyproject.toml
+├── .gitignore
+├── .github/workflows/ci.yml
+├── src/pytest_wardenbot/
+│   ├── __init__.py
+│   ├── plugin.py               # pytest plugin entry point + fixtures
+│   ├── adapters/
+│   │   ├── __init__.py
+│   │   ├── base.py             # ChatbotAdapter Protocol
+│   │   ├── http.py             # generic HTTP adapter
+│   │   ├── openai_chat.py      # optional
+│   │   └── anthropic_msgs.py   # optional
+│   ├── runners/
+│   │   ├── __init__.py
+│   │   └── base.py             # AttackRunner Protocol (for RAMPART hook in v0.2)
+│   ├── tests/                  # the shipped tests
+│   │   ├── __init__.py
+│   │   ├── test_prompt_injection.py
+│   │   ├── test_system_prompt_leak.py
+│   │   ├── test_refusal_bypass.py
+│   │   ├── test_business_truth.py
+│   │   ├── test_off_topic.py
+│   │   └── test_semantic.py    # optional, requires [judge] extra
+│   ├── grading/
+│   │   ├── __init__.py
+│   │   ├── deterministic.py
+│   │   └── judge.py            # optional, requires [judge] extra
+│   ├── corpus/                 # canonical attack strings
+│   │   ├── __init__.py
+│   │   ├── jailbreak.py
+│   │   ├── leak_elicitation.py
+│   │   └── refusal_patterns.py
+│   └── remediation.py          # agent-ready Markdown formatter
+├── tests/                       # tests OF the plugin itself
+│   ├── conftest.py
+│   ├── test_adapters.py
+│   ├── test_grading.py
+│   ├── test_plugin.py
+│   └── fixtures/
+│       └── mock_chatbot.py
+├── examples/
+│   ├── README.md
+│   ├── basic_http.py
+│   ├── openai_assistant.py
+│   └── github_actions.yml
+└── docs/
+    └── (deferred to session 6 — mkdocs-material)
+```
+
+---
+
+## Session breakdown
+
+Each session is sized for ~half-day to full-day of focused work. Doable across 2–3 weekends or 2 weeks of evening sessions.
+
+### Session 1 — Scaffold + first working test (today)
+
+**Scope:** Get to a state where `pip install -e .` works AND `pytest` discovers and runs at least one wardenbot test against a mock chatbot.
+
+**Deliverables:**
+- `pyproject.toml` with metadata, deps, extras
+- `.gitignore` for Python projects
+- `src/pytest_wardenbot/__init__.py` + version
+- `src/pytest_wardenbot/adapters/base.py` — `ChatbotAdapter` Protocol
+- `src/pytest_wardenbot/adapters/http.py` — `HTTPChatbotAdapter`
+- `src/pytest_wardenbot/plugin.py` — pytest plugin entry point with a `chatbot` fixture
+- `src/pytest_wardenbot/tests/test_prompt_injection.py` — ONE deterministic prompt-injection test
+- `src/pytest_wardenbot/corpus/jailbreak.py` — small starter corpus (5 entries)
+- `src/pytest_wardenbot/grading/deterministic.py` — `assert_no_harmful_content` helper
+- `src/pytest_wardenbot/remediation.py` — basic Markdown formatter
+- `tests/fixtures/mock_chatbot.py` — in-memory chatbot for testing the plugin itself
+- `tests/test_plugin.py` — at least one assertion that the plugin loads + the test runs
+- `.github/workflows/ci.yml` — lint + test on push
+- README slightly improved (still minimal; full marketing wait until launch)
+
+**DoD:**
+- `pip install -e .` succeeds locally
+- `pytest tests/` passes (plugin's own tests)
+- A user can write a `conftest.py` that registers an `HTTPChatbotAdapter`, then `pytest --pyargs pytest_wardenbot.tests` runs the shipped test against it
+- CI passes on push
+
+### Session 2 — Fill out the deterministic test corpus
+
+**Scope:** Author the remaining 14 deterministic tests + their corpus entries.
+
+**Deliverables:**
+- 5 prompt-injection variants (jailbreak fragments, "ignore previous instructions" variants, prompt-leak triggers, payload smuggling)
+- 3 system-prompt leak elicitation tests
+- 3 refusal-bypass tests (role-play, "for educational purposes", DAN-style)
+- 2 business-truth helpers (`assert_truth_fact_match`, supports exact / substring / numeric)
+- 2 off-topic deflection tests
+- Each test ships with a structured failure message + agent-ready remediation Markdown
+- Corpus entries grow to a reasonable starter set (~50 attack strings across categories)
+
+**DoD:**
+- All 15 deterministic tests pass against a known-safe mock chatbot
+- Each test fails predictably against a known-vulnerable mock chatbot (a fixture that intentionally fails specific patterns)
+- 80%+ coverage on the plugin code
+
+### Session 3 — Optional LLM-judge tests (DeepEval extra)
+
+**Scope:** Add the 5 optional tests that require an LLM judge.
+
+**Deliverables:**
+- `src/pytest_wardenbot/grading/judge.py` — DeepEval wrapper
+- `src/pytest_wardenbot/tests/test_semantic.py` — 5 semantic checks (semantic equivalence, brand alignment, hallucination, off-policy answer, refusal quality)
+- DAG-style rubrics following the three-layer-grading discipline from the main plan (`15-continuous-monitoring.md §4.1`)
+- Clear documentation about API key requirement
+- Tests are auto-skipped if `[judge]` extra isn't installed
+
+**DoD:**
+- `pip install pytest-wardenbot[judge]` works
+- LLM-judge tests run against a known-correct chatbot using a user-supplied API key
+- LLM-judge tests skip gracefully if extra not installed or API key missing
+- Cost-per-run for the 5 LLM-judge tests is documented (~$0.02 against Haiku)
+
+### Session 4 — DX polish + quickstart command
+
+**Scope:** Make the install-to-first-test path under 60 seconds.
+
+**Deliverables:**
+- `pytest-wardenbot --quickstart` CLI command (via pytest entry point) that generates a starter `conftest.py` + `test_my_bot.py` in the current directory
+- Industry templates: e-commerce, SaaS support, generic
+- Verbose failure messages with agent-ready Markdown
+- Custom pytest markers: `@pytest.mark.wardenbot`, `@pytest.mark.severity('high'|'medium'|'low')`
+- `examples/` directory with 3 worked examples (basic HTTP, OpenAI Assistant, GitHub Actions integration)
+- Updated README with the install-to-first-test quickstart
+
+**DoD:**
+- A new user can go from `pip install pytest-wardenbot` to first green test in under 60 seconds (verified by stopwatch)
+- Examples all run cleanly against test fixtures
+
+### Session 5 — CI + repo polish
+
+**Scope:** GitHub repo hygiene that makes the project look maintained.
+
+**Deliverables:**
+- GitHub Actions: lint (`ruff`), typecheck (`pyright` strict), tests across Python 3.11/3.12/3.13, coverage report
+- `pre-commit` config
+- Issue templates (bug report, feature request, test request)
+- Pull request template
+- `CONTRIBUTING.md` with the "out of scope" rule documented (anything the SaaS does is out of scope for the plugin)
+- `CODE_OF_CONDUCT.md`
+- `SECURITY.md` (per pytest-dev convention)
+- Badges in README: PyPI version, Python versions supported, CI status, coverage, downloads/month
+
+**DoD:**
+- All CI runs green
+- 85%+ test coverage
+- Pre-commit hooks catch issues locally
+
+### Session 6 — Docs site
+
+**Scope:** A real documentation site, not just a README.
+
+**Deliverables:**
+- `mkdocs-material` setup in `/docs`
+- Site published via GitHub Pages at `pytest-wardenbot.wardenbot.ai` (or `wardenbot.github.io/pytest-wardenbot` for v0.1)
+- Pages: Quickstart (60-second install-to-test), Per-test docs (what each test catches, why it matters), Adapter how-to ("add your chatbot"), Custom tests how-to, FAQ, Changelog, API reference auto-generated
+- Cross-link from README
+
+**DoD:**
+- Docs site live and navigable
+- Quickstart actually works for a new user following only the docs
+
+### Session 7 — Launch
+
+**Scope:** Coordinated PyPI release + community launch sequence.
+
+**Deliverables:**
+- PyPI release of `pytest-wardenbot 0.1.0`
+- GitHub repo: tagged release with release notes
+- Submit PR to pytest-dev/pytest plugin list
+- Launch posts (drafted in advance; published staggered):
+  - Day 1: personal dev.to / blog post
+  - Day 2: /r/Python "Show /r/Python"
+  - Day 3: /r/LangChain "I built a pytest plugin for chatbot testing"
+  - Day 4: Show HN
+  - Day 5: Twitter/X with demo GIF
+- Day 6–7: DM ~20 LLM-app maintainers with personalized pitch
+- README updated with marketing-flavored hero section
+
+**DoD:**
+- Package live on PyPI; `pip install pytest-wardenbot` works for anyone
+- First external star / issue / install
+- Listed on pytest's official plugin list
+
+---
+
+## Working metrics (month 1 post-launch)
+
+From the plugin-distribution research:
+
+| Metric | Healthy | Failing |
+|---|---|---|
+| PyPI installs/week | 500+ | <100 |
+| GitHub stars | 100+ | <20 |
+| Inbound real-user issues | 5+ | 0 |
+| External blog mentions | 3+ | 0 |
+| Click-through on upgrade footer | 2%+ | <0.5% |
+
+If at week 6 we're <100 installs/week with no external mentions, the *framing* is wrong (not the channel). Re-evaluate before sinking more time.
+
+---
+
+## Out of scope for v0.1 (deferred to v0.2+)
+
+To keep v0.1 launchable, these wait:
+
+- RAMPART runner (v0.2 — gated to `[agentic]` extra)
+- LangChain / MCP / Slack / Discord adapters (v0.2)
+- Authenticated "run against your WardenBot AI subscription" mode (v0.3, requires the SaaS to exist)
+- Custom corpus uploads (v0.3 — Sentry+ tier feature)
+- Multi-turn attack chains beyond basic (v0.2 — full PyRIT integration)
+- Browser-recon adapter (Castle/Sentry feature; doesn't belong in OSS)
+- `pytest-wardenbot --report-html` (nice-to-have, defer to v0.2)
+- pytest-html report integration (v0.2)
+
+---
+
+## Upgrade CTA strategy (intake form for now)
+
+Until the managed SaaS launches, the plugin's footer message on every test run:
+
+```
+30 tests passed. ✅
+Want continuous monitoring across all your bots, daily? Tell us about your setup → wardenbot.ai/intake/
+```
+
+No "subscribe now" CTAs. No bait-and-switch. The plugin's value stands alone; the upgrade path is honest about the SaaS not being live yet.
+
+When the SaaS launches in Wave 6, this footer changes to a real signup link.
+
+---
+
+## Maintenance commitment
+
+- ~10–20% of one engineer's time, indefinitely.
+- Triage rule: anything the SaaS will do is **out of scope** for the plugin (documented in CONTRIBUTING.md). Politely decline PRs that try to add SaaS-like features.
+- Monthly minor release on the second Tuesday: dependency updates, small test additions, bug fixes.
+- Major releases (breaking changes): no more than annually, with 6-month deprecation warnings.
+- Telemetry: **opt-in only**. Never default-on. Never phone home.
+- License: Apache 2.0 forever. **No license rugpulls** (HashiCorp / ElasticSearch / MongoDB taught the lesson).
+
+---
+
+## TL;DR
+
+7 sessions, ~2–3 weeks of focused founder time, to ship `pytest-wardenbot 0.1.0`. Defer RAMPART to v0.2 (alpha software + agentic-only relevance). Ship 30 deterministic tests + 5 optional LLM-judge case factories + opt-in canary-leak test. Lean install, frictionless first-test path, honest intake-form CTA. Start today with Session 1.

pytest_wardenbot-0.1.0/LICENSE.md

@@ -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.