memtrust 0.1.0__tar.gz

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

@@ -0,0 +1,62 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+permissions:
+  contents: read
+
+jobs:
+  lint:
+    name: Lint (ruff)
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4.3.1
+      - uses: actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065 # v5.6.0
+        with:
+          python-version: "3.12"
+      - run: pip install ruff
+      - run: ruff check .
+      - run: ruff format --check .
+
+  typecheck:
+    name: Type check (mypy --strict)
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4.3.1
+      - uses: actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065 # v5.6.0
+        with:
+          python-version: "3.12"
+      - run: pip install -e ".[dev]"
+      - run: mypy --strict src/memtrust
+
+  test:
+    name: Test (pytest + coverage)
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4.3.1
+      - uses: actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065 # v5.6.0
+        with:
+          python-version: ${{ matrix.python-version }}
+      - run: pip install -e ".[dev]"
+      # All tests run fully offline -- no vendor or judge API keys are
+      # configured here, and none are required. This is what proves the
+      # "never crash on missing credentials" contract on every push.
+      - run: pytest --cov=memtrust --cov-report=term-missing --cov-fail-under=80
+
+  security:
+    name: Security (pip-audit)
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4.3.1
+      - uses: actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065 # v5.6.0
+        with:
+          python-version: "3.12"
+      - run: pip install -e ".[dev]"
+      - run: pip-audit

memtrust-0.1.0/.gitignore

@@ -0,0 +1,25 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+.eggs/
+build/
+dist/
+.venv/
+venv/
+.env
+.env.*
+!.env.example
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+.coverage.*
+htmlcov/
+coverage.xml
+*.log
+.DS_Store
+results/*/
+!results/.gitkeep
+node_modules/
+.idea/
+.vscode/

memtrust-0.1.0/.pre-commit-config.yaml

@@ -0,0 +1,17 @@
+repos:
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.15.9
+    hooks:
+      - id: ruff
+        args: [--fix]
+      - id: ruff-format
+
+  - repo: https://github.com/pre-commit/mirrors-mypy
+    rev: v1.14.1
+    hooks:
+      - id: mypy
+        args: [--strict, src/memtrust]
+        pass_filenames: false
+        additional_dependencies:
+          - httpx>=0.27.0
+          - click>=8.1.7

memtrust-0.1.0/CHANGELOG.md

@@ -0,0 +1,58 @@
+# Changelog
+
+All notable changes to this project are documented here. Format loosely follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
+
+## [Unreleased]
+
+### Added
+
+- `npm/` -- an unpublished npm-distributable CLI wrapper (`npx memtrust ...`) for CI and agent
+  runners that have Node.js but not necessarily a Python toolchain. Six per-platform optional
+  packages (`@memtrust/darwin-arm64`, `darwin-x64`, `linux-arm64`, `linux-x64`, `win32-arm64`,
+  `win32-x64`) each bundle a genuine, SHA-256-verified copy of Astral's `uv` binary
+  (github.com/astral-sh/uv, dual-licensed MIT OR Apache-2.0), fetched from uv's own GitHub
+  release 0.11.28 at npm package-publish time via a `prepack` script, never at end-user install
+  time. The `memtrust` bin shim runs `uv tool run --from memtrust memtrust <args>`, which
+  bootstraps a Python interpreter and installs `memtrust` from PyPI on first use. Not yet
+  published to npm -- gated on a separate publish step. See the README's "npx (agent-native)"
+  section and `npm/` for the wrapper source and third-party attribution.
+
+## [0.1.0] - 2026-07-11
+
+Initial release.
+
+### Added
+
+- Shared `MemoryBackendAdapter` interface (`store()`/`query()`/`update()`) in
+  `src/memtrust/adapters/base.py`, plus `ConflictSignal` classification used by the
+  contradiction-detection eval.
+- Four backend adapters: MemPalace, Mem0, Zep/Graphiti, OpenViking. Each reads its configuration
+  from a single environment variable and raises `BackendNotConfiguredError` (never crashes) when
+  it's missing. Confidence level per adapter documented in `docs/methodology.md`.
+- Three eval runners: LongMemEval-style long-horizon recall, LoCoMo-style multi-session recall,
+  and memtrust's original multi-hop contradiction-detection eval (flagged / silently-overwrote /
+  served-stale / not-applicable).
+- LLM-judge scoring pipeline (`scoring/llm_judge.py`), model-configurable via environment
+  variables, with a no-crash `NOT_RUN` fallback when no judge API key is configured.
+- Cost tracker (`scoring/cost_tracker.py`) with a dated, approximate per-model pricing table.
+- `memtrust run` and `memtrust report` CLI commands.
+- Static leaderboard site (`leaderboard/index.html` + `leaderboard/data.json`) with a documented
+  schema, shipped as an example rather than fabricated live results.
+- Full test suite: 57 tests, 95% overall coverage, 100% on `adapters/base.py`,
+  `evals/contradiction.py`, `evals/longmemeval.py`, and `scoring/`. All tests run fully offline.
+- CI workflow: lint (ruff), type-check (mypy --strict), test (pytest + coverage across Python
+  3.11-3.13), security (pip-audit).
+- `docs/methodology.md`, `CONTRIBUTING.md`, `SECURITY.md`.
+
+### Known limitations (v0.1)
+
+- Adapters for MemPalace and OpenViking are built against best-effort interpretations of
+  documented product concepts, not a confirmed API reference -- see the confidence table in
+  `docs/methodology.md`. They should be verified against a live instance before their output is
+  treated as authoritative.
+- LongMemEval and LoCoMo eval runners ship against small, explicitly synthetic sample fixtures
+  matching each benchmark's real published schema, not the full public datasets.
+- No live benchmark numbers are published in the README -- running the harness against real
+  backends requires vendor API keys not available at the time of this release. See the README's
+  "Benchmarks" section for exactly what was and wasn't measured.

memtrust-0.1.0/CLAUDE.md

@@ -0,0 +1,106 @@
+# CLAUDE.md -- memtrust
+
+## Project identity
+
+- **What this is:** an independent, reproducible benchmark harness that runs standardized evals
+  (LongMemEval, LoCoMo, and an original multi-hop contradiction-detection eval) against
+  agent-memory backends (MemPalace, Mem0, Zep/Graphiti, OpenViking) and publishes results with
+  full raw logs and a documented methodology.
+- **Repo:** github.com/RudrenduPaul/memtrust
+- **Package:** `memtrust` on PyPI
+- **Language:** Python (`src/memtrust/` layout, PEP 621 `pyproject.toml`)
+- **License:** Apache 2.0
+- **Goal:** be the benchmark someone can point to instead of a vendor's own self-reported number,
+  because the methodology, prompts, and raw logs are fully public and reproducible from a fresh
+  clone. Trust is earned by being independently reproducible, not claimed.
+
+## Git workflow
+
+When asked to commit, push, or "update GitHub" -- just do it. No confirmation prompts.
+
+- `git add` relevant files -> `git commit` -> `git push origin main` in one shot.
+- Every commit message ends with:
+  `Built by Rudrendu Paul and Sourav Nandy, developed with Claude Code`
+- Do not add `Co-Authored-By:` trailers.
+- Prefer small, checkpoint-shaped commits over one giant commit.
+
+## Engineering standards (block all tasks until these pass)
+
+1. **Lint:** `ruff check . && ruff format --check .`
+2. **Types:** `mypy --strict src/memtrust` -- zero errors, zero unexplained `# type: ignore`.
+3. **Tests:** `pytest --cov=memtrust --cov-report=term-missing --cov-fail-under=80` -- 80% minimum
+   overall; 90%+ on `adapters/base.py`, `evals/contradiction.py`, and `scoring/`. Every test must
+   run fully offline -- mock or stub any network/vendor call. No test may require a real API key.
+4. **Security:** `pip-audit` -- no unfixed HIGH/CRITICAL CVEs in the dependency tree.
+5. **Reproducibility:** if you changed a scoring prompt, an adapter, or an eval dataset version,
+   re-run the affected eval and show the before/after in your response -- never state a number
+   without showing the command that produced it.
+
+Do not mark a task complete if any of these fail. Fix the root cause; do not suppress errors or
+add a blanket `# type: ignore`.
+
+## Planning rules
+
+Enter plan mode for any task that:
+- Touches more than 2 files.
+- Changes the `MemoryBackendAdapter` interface or a scoring-pipeline contract.
+- Adds a new eval family or a new tracked backend.
+- Modifies `.github/workflows/ci.yml`.
+
+Write the plan before touching code. If something goes wrong mid-task, stop and re-plan rather
+than patching around the original plan.
+
+## Anti-sycophancy rules
+
+These override default behavior in every session working on this repo:
+
+1. **No benchmark number without a fresh, reproducible run.** Before publishing or citing a score
+   for any backend, run the eval and show the command output. Never state a number from memory or
+   a stale prior run without re-verifying it's current.
+2. **Every eval runs identically across every tracked backend.** No per-vendor prompt tuning, no
+   per-vendor dataset subset. If a backend's API genuinely cannot support a given eval, document
+   the gap explicitly in the results (`ConflictSignal.NOT_APPLICABLE`, or an equivalent explicit
+   marker) rather than silently excluding the backend from that eval's table.
+3. **No "verified"/"safe"/"best" claim about any backend.** This project publishes comparative
+   scores across a defined eval set, not an endorsement or a safety certification. Report numbers;
+   let the reader draw the conclusion.
+4. **Every methodology decision lives in `docs/methodology.md`, versioned with the code.** Prompt
+   templates, dataset versions, scoring rubrics, and adapter confidence levels all belong there. If
+   a methodology choice can't be explained in that file, it does not belong in the harness.
+5. **Vendor-pushback check.** Before publishing a run, ask: "if this backend's own maintainers
+   read this methodology, could they point to a specific, defensible flaw?" If yes, fix the flaw
+   before publishing, not after someone complains publicly.
+
+## What Claude must never do in this repo
+
+- Publish or cite a benchmark number without a fresh command-output run in the same session.
+- Ship a new eval or backend adapter without a corresponding `docs/methodology.md` entry.
+- Commit with `--no-verify`.
+- Merge a change to scoring logic without re-running the affected eval and showing the delta.
+- Present a best-effort adapter (see the confidence table in `docs/methodology.md`) as a confirmed
+  vendor API integration.
+- State or imply that this project's purpose is anything other than the eval harness and
+  leaderboard described above.
+
+## Key files
+
+| File | Purpose |
+|---|---|
+| `src/memtrust/adapters/base.py` | The shared adapter interface every backend implements. Read this before touching any adapter. |
+| `src/memtrust/adapters/` | One adapter per backend (MemPalace, Mem0, Zep/Graphiti, OpenViking). |
+| `src/memtrust/evals/contradiction.py` | The original wedge eval -- the most important file in the repo. |
+| `src/memtrust/evals/` | LongMemEval and LoCoMo runners. |
+| `src/memtrust/scoring/` | LLM-judge scoring pipeline and cost tracker. |
+| `src/memtrust/cli.py` | `memtrust run`, `memtrust report`. |
+| `docs/methodology.md` | Full, versioned methodology -- read before publishing any number. |
+| `leaderboard/` | Static leaderboard site (`index.html` + `data.json`). |
+| `CONTRIBUTING.md` | Read before adding a new backend adapter -- the primary contribution path. |
+| `.github/workflows/ci.yml` | lint -> type-check -> test -> security. |
+
+## Session start checklist
+
+1. Run `git status` and `git log --oneline -5` to understand current state.
+2. Run `pytest` to confirm the baseline is green before touching anything.
+3. Read `docs/methodology.md`'s relevant section before changing an eval or adapter.
+4. If a score looks off, re-run the specific eval against the specific backend with verbose output
+   before assuming the harness (rather than the backend) is wrong.

memtrust-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,117 @@
+# Contributing
+
+The easiest and most useful way to contribute is adding a new backend adapter. This document
+covers that path in detail, plus the general workflow for everything else.
+
+## Adding a new backend adapter
+
+Every adapter implements `memtrust.adapters.base.MemoryBackendAdapter`, defined in
+`src/memtrust/adapters/base.py`. Read that file first; it is short and it is the actual contract,
+not a summary of one.
+
+### The interface
+
+```python
+class MemoryBackendAdapter(ABC):
+    name: str
+    env_var: str
+    supports_update: bool = True
+
+    def store(self, session_id: str, content: str, metadata: dict[str, str] | None = None) -> StoreResult: ...
+    def query(self, session_id: str, query: str, top_k: int = 5) -> QueryResult: ...
+    def update(self, session_id: str, memory_id: str, content: str) -> UpdateResult: ...
+```
+
+### Step by step
+
+1. **Pick your `env_var`.** Every adapter reads exactly one environment variable in `__init__` and
+   raises `BackendNotConfiguredError(self.name, self.env_var)` immediately if it's missing --
+   never on the first method call. This is what lets `memtrust run` report SKIPPED instead of
+   crashing when a backend isn't configured. If your backend genuinely needs no secret (like
+   MemPalace, which is local-first), gate on whatever configuration value it does need instead --
+   see `mempalace_adapter.py` for the pattern and `docs/methodology.md` for why.
+
+2. **Implement `store()`, `query()`, `update()`** against the vendor's real API. Wrap every
+   network/vendor failure in `BackendAPIError(self.name, detail)` -- never let a raw
+   `httpx.HTTPError` or vendor SDK exception escape the adapter. `query()` must return a
+   `ConflictSignal` (see below).
+
+3. **Report `ConflictSignal` honestly.** This is what the contradiction-detection eval reads.
+   - `FLAGGED` if your backend's response makes a contradiction visible (returns both old and new
+     values, an explicit conflict marker, an invalidation timestamp, etc.)
+   - `NOT_APPLICABLE` if you cannot determine this from the response -- do **not** guess `FLAGGED`
+     or `SILENT_OVERWRITE` to make a number look better. The contradiction eval independently
+     cross-checks your reported signal against the actual retrieved content (see
+     `evals/contradiction.py::classify_case`), so an inflated self-report gets caught and
+     downgraded, not rewarded.
+   - If your backend has no update/contradiction-relevant primitive at all, set
+     `supports_update = False` on the class. The eval then records `NOT_APPLICABLE` for every case
+     without calling your adapter, and that gap is shown explicitly in results tables -- it is
+     never silently dropped.
+
+4. **Document your confidence level.** At the top of your adapter file, write a docstring stating
+   what you verified against real vendor documentation and what you built as best-effort. Add a
+   row to the confidence table in `docs/methodology.md`. If you are not confident about an exact
+   endpoint path or method signature, say so in the code comment at the point of use, the same way
+   `mempalace_adapter.py` and `openviking_adapter.py` do. A wrong guess that's labeled is useful; a
+   wrong guess presented as confirmed is a bug that will mislead every leaderboard reader.
+
+5. **Register it.** Add your adapter class to `ADAPTER_REGISTRY` in
+   `src/memtrust/adapters/__init__.py`, keyed by the name users will pass to `--backends`.
+
+6. **Write tests.** Every adapter test mocks the HTTP layer (`pytest-httpx`) or injects a fake
+   object matching your adapter's expected vendor interface -- see `tests/test_adapters.py` for
+   the pattern used by all four existing adapters. No test may make a real network call. Cover at
+   minimum: `BackendNotConfiguredError` when the env var is missing, a successful `store`/`query`/
+   `update` round trip against a mocked response, and a `BackendAPIError` on a failed HTTP call.
+
+7. **Run the full check before opening a PR:**
+   ```bash
+   ruff check . && ruff format --check .
+   mypy --strict src/memtrust
+   pytest --cov=memtrust --cov-report=term-missing --cov-fail-under=80
+   pip-audit
+   ```
+
+### What a PR adding an adapter should include
+
+- The adapter file, following the pattern above.
+- Its registration in `ADAPTER_REGISTRY`.
+- Tests in `tests/test_adapters.py`.
+- A confidence-level entry in `docs/methodology.md`'s adapter table.
+- A one-line addition to the README's backend coverage table.
+
+## Adding or extending an eval
+
+The three eval families live in `src/memtrust/evals/`. Each is a plain function taking a
+configured `MemoryBackendAdapter` (and an `LLMJudge` for the two that need semantic grading) and
+returning a dataclass of results -- there is no plugin system to learn, just a function signature
+to match. See `evals/contradiction.py` for the simplest example (no LLM judge needed) and
+`evals/longmemeval.py` for the LLM-judged pattern.
+
+To extend the contradiction-detection eval's case set, add entries to
+`tests/fixtures/contradiction_cases.json`. Read `docs/methodology.md`'s note on how the
+`contradicting_fact` field should be phrased before adding a case -- a correction that restates
+the old value inside its own text can produce a misleading classification (this happened once
+during the initial build and is documented there in detail).
+
+To run the harness against the real, full LongMemEval or LoCoMo datasets instead of the bundled
+synthetic samples, see the "to run against the real dataset" note under each eval in
+`docs/methodology.md` -- both loaders accept a `dataset_path` argument already; only a format
+conversion (or a second loader function) is needed.
+
+## General workflow
+
+1. Fork, branch, make your change.
+2. Run the full check list above locally before pushing.
+3. Keep PRs scoped to one adapter, one eval change, or one clearly-described fix -- easier to
+   review, easier to bisect if something regresses.
+4. Every claim in a PR description about a score or benchmark number must be reproducible from a
+   command someone else can run. "I ran X and got Y" needs the X.
+
+## Code of conduct
+
+Be direct, be specific, assume good faith. Disagreement about a methodology choice is welcome and
+expected -- open an issue with the specific flaw, not a vague complaint. This project exists
+because vague, unverifiable claims about agent-memory backends are the problem it's trying to fix;
+holding contributions to the same standard is the point.

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