datacharter 0.1.0__tar.gz

datacharter-0.1.0/.github/workflows/banned-terms.yml

@@ -0,0 +1,26 @@
+name: banned-terms
+
+# Release-hygiene gate: certain terms must never appear in this codebase,
+# in any file, on any branch. The patterns below use single-character
+# classes (e.g. "[p]attern") so this workflow file never contains the
+# literal terms it bans — meaning the check can ship in the public repo
+# without flagging itself.
+
+on:
+  push:
+  pull_request:
+
+jobs:
+  scan:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Scan for banned terms
+        run: |
+          set -e
+          PATTERN='[p]anasonic|[k]anpai|[a]idp|[g]aai|[p]rdca|[y]ohana|[p]well'
+          if grep -riE "$PATTERN" --exclude-dir=.git .; then
+            echo "::error::Banned term found — see matches above."
+            exit 1
+          fi
+          echo "Clean."

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

@@ -0,0 +1,51 @@
+# Publishes to PyPI via Trusted Publishing (OIDC) — no stored token.
+#
+# One-time PyPI setup (Project → Publishing → Add a pending publisher):
+#   PyPI Project name: datacharter
+#   Owner:             datacharter
+#   Repository name:   datacharter
+#   Workflow filename: release.yml
+#   Environment name:  pypi
+# Then create a GitHub Release (tag like v0.1.0) to trigger this workflow.
+name: release
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 22
+          cache: npm
+          cache-dependency-path: ui/package-lock.json
+      - uses: astral-sh/setup-uv@v4
+      - name: Build UI into the package
+        run: ./scripts/build_ui.sh
+      - name: Build sdist + wheel
+        run: uv build
+      - name: Validate metadata and README rendering
+        run: uvx twine check dist/*
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/project/datacharter/
+    permissions:
+      id-token: write # OIDC token for PyPI Trusted Publishing
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1

datacharter-0.1.0/.github/workflows/test.yml

@@ -0,0 +1,91 @@
+name: test
+
+on:
+  push:
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v4
+      - name: Install
+        run: uv venv && uv pip install -e ".[dev]"
+      - name: Lint
+        run: .venv/bin/ruff check .
+      - name: Unit tests
+        run: .venv/bin/pytest -q
+
+  integration:
+    runs-on: ubuntu-latest
+    services:
+      postgres:
+        image: postgres:16-alpine
+        env:
+          POSTGRES_USER: charter
+          POSTGRES_PASSWORD: charter_test_pw
+          POSTGRES_DB: demo
+        ports:
+          - 55432:5432
+        options: >-
+          --health-cmd "pg_isready -U charter -d demo"
+          --health-interval 2s --health-timeout 2s --health-retries 30
+      mysql:
+        image: mysql:8.4
+        env:
+          MYSQL_ROOT_PASSWORD: root_test_pw
+          MYSQL_USER: charter
+          MYSQL_PASSWORD: charter_test_pw
+          MYSQL_DATABASE: demo
+        ports:
+          - 53306:3306
+        options: >-
+          --health-cmd "mysqladmin ping -h 127.0.0.1 -pcharter_test_pw -ucharter"
+          --health-interval 2s --health-timeout 2s --health-retries 60
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v4
+      - name: Install
+        run: uv venv && uv pip install -e ".[dev]"
+      - name: Seed databases
+        run: |
+          sudo apt-get install -y -q postgresql-client mysql-client >/dev/null
+          PGPASSWORD=charter_test_pw psql -h 127.0.0.1 -p 55432 -U charter -d demo \
+            -f tests/integration/seed/postgres.sql
+          mysql -h 127.0.0.1 -P 53306 -ucharter -pcharter_test_pw demo \
+            < tests/integration/seed/mysql.sql
+      - name: Integration tests
+        run: .venv/bin/pytest -m integration -q
+
+  ui:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 22
+          cache: npm
+          cache-dependency-path: ui/package-lock.json
+      - name: Install
+        run: cd ui && npm ci
+      - name: Typecheck + build
+        run: cd ui && npm run build
+
+  package:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 22
+          cache: npm
+          cache-dependency-path: ui/package-lock.json
+      - uses: astral-sh/setup-uv@v4
+      - name: Build UI into package
+        run: ./scripts/build_ui.sh
+      - name: Install + e2e
+        run: |
+          uv venv
+          uv pip install -e ".[dev]"
+          .venv/bin/pytest -m e2e -q

datacharter-0.1.0/.gitignore

@@ -0,0 +1,35 @@
+# Python
+__pycache__/
+*.py[cod]
+.venv/
+venv/
+dist/
+build/
+*.egg-info/
+.pytest_cache/
+.ruff_cache/
+.coverage
+
+# Node
+node_modules/
+*.local
+
+# Env / secrets
+.env
+.env.*
+!.env.example
+
+# DuckDB local artifacts
+*.duckdb
+*.duckdb.wal
+
+# OS / editor
+.DS_Store
+.idea/
+.vscode/
+
+# UI build output (built in CI / at release)
+ui/dist/
+ui/*.tsbuildinfo
+src/datacharter/server/static/
+.claude/

datacharter-0.1.0/.impeccable/hook.cache.json

@@ -0,0 +1 @@
+{"version":1,"sessions":{"4526dd9e-e6b7-4c46-91fd-b88f1a601f85":{"updatedAt":1784780655809,"files":{"/Users/rishi.mashelkar/Desktop/git-repo/datacharter/ui/vite.config.ts":{"editCount":1,"findings":[]},"/Users/rishi.mashelkar/Desktop/git-repo/datacharter/ui/index.html":{"editCount":1,"findings":[]},"/Users/rishi.mashelkar/Desktop/git-repo/datacharter/ui/src/api.ts":{"editCount":2,"findings":[]},"/Users/rishi.mashelkar/Desktop/git-repo/datacharter/ui/src/main.tsx":{"editCount":1,"findings":[]},"/Users/rishi.mashelkar/Desktop/git-repo/datacharter/ui/src/styles.css":{"editCount":3,"findings":[]},"/Users/rishi.mashelkar/Desktop/git-repo/datacharter/ui/src/components/SourceTree.tsx":{"editCount":1,"findings":[]},"/Users/rishi.mashelkar/Desktop/git-repo/datacharter/ui/src/components/ResultsGrid.tsx":{"editCount":2,"findings":[]},"/Users/rishi.mashelkar/Desktop/git-repo/datacharter/ui/src/App.tsx":{"editCount":1,"findings":[]},"/Users/rishi.mashelkar/Desktop/git-repo/datacharter/ui/src/components/ChatPanel.tsx":{"editCount":1,"findings":[]}}}}}

datacharter-0.1.0/CHANGELOG.md

@@ -0,0 +1,80 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+Format: [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
+
+## [Unreleased]
+
+## [0.1.0] - 2026-07-23
+
+First public release.
+
+### Packaging
+
+- Self-contained wheel: the web UI is bundled into the package, so
+  `pip install datacharter` (or `uvx datacharter`) runs the full app with
+  no Node toolchain and no repo checkout.
+
+### Added
+
+- Federation parity (D10): BigQuery and SQL Server via DuckDB community
+  extensions; Snowflake via connector-extract fallback; uniform
+  `source__table` compatibility views across every source; per-source
+  filter/projection pushdown with EXPLAIN-verified tests.
+- Connector pushdown planner (D11): deterministic, AST-driven filter +
+  projection pushdown into the Snowflake extract — no agent required. Connector
+  tables now materialize lazily with each query's pushdown applied and cached.
+- Large-dataset handling (D12): connector extracts now report truncation via
+  `QueryResult.warnings` (UI banner + agent), a per-source `max_rows:` cap in
+  charter.yaml, and aggregation pushdown that runs single-table GROUP BY queries
+  on the remote instead of extracting raw rows.
+- Aggregation pushdown now also covers export and snapshots (D12): a pushable
+  single-table aggregation is computed on the remote and its small result staged
+  locally for `COPY`/snapshot, instead of raw-extracting (and capping) the table.
+  Pushed `ORDER BY` emits explicit `NULLS FIRST`/`NULLS LAST` so the remote row
+  order matches the local result deterministically.
+- Virtualized results grid: only visible rows render to the DOM, so the grid
+  scrolls a full 10k-row result smoothly (default visible cap raised 1k → 10k).
+- `datacharter secrets set|list|rm` — manage `${NAME}` secrets in the OS keyring.
+
+### Security
+
+- Read-only guard rewritten on DuckDB's parser: counts and types statements and
+  blocks filesystem/remote functions. Closes verified bypasses — dollar-quote
+  statement stacking, `EXPLAIN ANALYZE COPY` file writes, CTE-prefixed DML, and
+  arbitrary file reads via `read_csv`/`glob`/`postgres_scan`.
+- HTTP surface hardened: Host-header allowlist (anti-DNS-rebinding) plus Origin
+  and Sec-Fetch-Site checks reject cross-site browser requests.
+- Local state DB is now encrypted (key from the OS keyring or
+  `DATACHARTER_STATE_KEY`); connector literals escape backslash as well as quote;
+  sync DB access is serialized; uploads are size-bounded and export temp files
+  are cleaned up.
+
+- Natural-language agent: `/api/agent/ask` SSE endpoint and chat panel.
+  4-tool loop (list_sources/list_tables/describe_table/query) over any
+  OpenAI-compatible endpoint via a dependency-free httpx client; charter
+  PII columns masked in tool results; `serve --local` targets Ollama
+  (qwen3:8b default). Agent can emit inline Vega-Lite charts.
+
+- Local server: `datacharter serve` (localhost-only by default, port 8321)
+  with JSON API (`/api/health|sources|tables|query|profile`), SSE query
+  streaming with heartbeats, scrubbed error envelope, and ephemeral demo
+  workspace when run without a charter.
+
+- charter.yaml loader: `${NAME}` secret resolution (env → .env → OS
+  keyring), hard error on credential literals with fix-it guidance,
+  workspace portability lint (absolute/backslash paths), contextual
+  error messages.
+- Iceberg and Delta source types.
+- `datacharter init`: workspace scaffolding (charter.yaml, queries/,
+  .env.example, .gitignore) with optional generated demo dataset.
+- Query engine core: DuckDB session bound to a workspace; postgres/mysql
+  (temporary-secret + read-only attach), sqlite, csv/parquet/json sources
+  (s3 paths supported); cross-source joins via native catalogs.
+- Read-only SQL guard: statement allowlist with `local.*` DDL as the only
+  write path; single-statement enforcement; comment-smuggling protection.
+- Encrypted local persistence catalog (`local`) for snapshots.
+- Spill hygiene: contained temp dir, always-on temp-file encryption,
+  wipe on start/close, optional no-spill mode.
+- Credential scrubbing on all engine error paths.
+- Async query API with interrupt-based timeouts.

datacharter-0.1.0/CLAUDE.md

@@ -0,0 +1,103 @@
+# DataCharter — Claude Code Project Context
+
+Contract-governed local data exploration. Tagline: "Charter your data."
+This file is the cross-machine source of truth for project context — keep it
+updated so any Claude session on any machine picks up where the last left off.
+
+## Current state
+
+See `docs/PROGRESS.md` (running journal — update it at the end of every
+working session, then push).
+
+## Locked decisions
+
+- **License:** Apache-2.0. **Repo:** private until V1; at V1 publish via fresh
+  `git init` + single curated commit into a NEW public repo (never flip this
+  repo public — dev history must not ship).
+- **Clean-room build.** All code written fresh for this repo. Never copy code
+  from any prior codebase.
+- **Hygiene gate:** `.github/workflows/banned-terms.yml` scans every push.
+  Never introduce a term its pattern matches — including in docs, comments,
+  and commit messages. Do not write those terms into this file either.
+- **Commit identity:** use the per-repo git identity already configured
+  (personal noreply address). Never commit with any employer-associated
+  account. Verify with `git config user.email` before first commit of a session.
+- **Name:** DataCharter (one word, capital D+C). Config file: `charter.yaml`.
+  Brand: `brand/` (hero.png = social/landing; mark.svg = favicon/avatar/README).
+
+## Architecture (planned)
+
+- **Engine:** Python + DuckDB federation. DB sources via native `ATTACH`
+  (postgres, mysql, sqlite, bigquery, mssql — community extensions where
+  needed), file sources via views (s3/gcs/azure/excel/csv/parquet/json),
+  Snowflake via connector fallback, Iceberg + Delta via core extensions.
+  Cross-source joins, `CREATE SECRET` credential injection, query timeouts
+  via interrupt, credential-scrubbed error messages.
+- **Sources:** `charter.yaml` — ODCS/datacontract-style YAML. Source type,
+  connection, `${ENV_VAR}` credential interpolation (.env), tables, PII field
+  lists (drive masking).
+- **Serving:** FastAPI, SSE/NDJSON streaming.
+- **Agent:** 4-tool loop (list_sources, list_tables, describe_table,
+  query). BYO `OPENAI_BASE_URL` default; `--local` mode
+  provisions Ollama + Qwen3 8B; phase-2: route SQL-writing to
+  Arctic-Text2SQL-R1-7B. Constrained JSON tool calls; schema pruning;
+  execution-feedback retry.
+- **UI:** Vite + React. Source tree, Monaco SQL editor, results grid
+  (tanstack), Vega-Lite spec-driven charts (agent emits specs; heuristic
+  auto-detect fallback), profiling panel (missing/percentiles/skew/outliers/
+  correlation), CSV/parquet/xlsx export, local file drag-drop.
+- **Packaging:** `pip install datacharter` / `uvx datacharter`.
+
+## MVP scope (~3–3.5 wk) then post-launch
+
+MVP = engine + charter.yaml + FastAPI + agent + UI + Tier-1 features
+(Iceberg/Delta, file drop, exports, EXPLAIN ANALYZE visualizer).
+Post-launch #1: **MCP server mode** (`datacharter mcp` — the 5 agent tools as
+MCP tools) + schema drift badges; then contract quality checks.
+
+## Conventions (binding)
+
+**Authorship & commits**
+- Commits, code comments, and docs must NOT mention Claude, AI assistance, or
+  any tooling attribution. No `Co-Authored-By` trailers, no session links.
+- Conventional Commits (`feat:`/`fix:`/`docs:`/`chore:`/`test:`/`refactor:`).
+  Subject ≤72 chars, imperative mood. Body only when the WHY isn't obvious.
+- Every commit must build and pass tests (bisectable history). Small, focused
+  commits over omnibus ones.
+
+**Code style**
+- Comments: max 2 lines, and only where the code can't say it — constraints,
+  invariants, non-obvious WHY. Never narrate WHAT the next line does.
+- Reusable components first: before writing new code, check for an existing
+  helper/component to extend. Extract shared logic once used twice (engine
+  utils, UI atoms, test fixtures alike).
+- Boring, explicit names. No cleverness. English-only identifiers.
+- Type hints on all function signatures. Docstrings (one-liner minimum) on
+  public API only — not private helpers.
+- Errors: actionable messages that say what to fix; never echo credentials
+  (scrub before raising — engine-wide invariant).
+
+**Dependencies & security**
+- Every new dependency needs a one-line justification in the PR/commit body.
+  Prefer stdlib/DuckDB-native. Lower-bound pins only (`>=`), no upper pins
+  without reason.
+- No secrets, tokens, or real hostnames in code, tests, or fixtures — ever.
+  `.env` locally, `.env.example` committed with placeholder values.
+
+**Testing**
+- Every feature lands with tests. Unit tests fast by default; integration
+  tests (docker) behind a marker so `pytest -q` stays quick.
+- Test names describe behavior (`test_join_across_postgres_and_parquet`),
+  not implementation.
+
+**Public-API discipline (for OSS consumers)**
+- `__all__` in public modules; anything else is private by convention (`_`).
+- Keep a `CHANGELOG.md` (Keep-a-Changelog format) from M1 onward.
+- Post-V1: semver; breaking changes only on majors.
+
+**Session ritual**
+- End each session: update `docs/PROGRESS.md` (done / in-flight / next),
+  check off `docs/PLAN.md` boxes, push.
+
+**V1 publish note:** `CLAUDE.md`, `docs/PROGRESS.md`, and `docs/PLAN.md` are
+dev-internal — review at release gate: publish cleaned versions or exclude.

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