open-evidence-verification 0.2.1__tar.gz

open_evidence_verification-0.2.1/.github/workflows/ci.yml

@@ -0,0 +1,66 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test:
+    name: test + lint + typecheck (Python ${{ matrix.python-version }})
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        # Keep in sync with requires-python and classifiers in pyproject.toml.
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v7
+
+      - uses: actions/setup-python@v6
+        with:
+          python-version: ${{ matrix.python-version }}
+          cache: pip
+
+      - name: Install
+        run: python -m pip install -e ".[dev]"
+
+      - name: Lint (ruff)
+        run: |
+          ruff check .
+          ruff format --check .
+
+      - name: Type-check (mypy)
+        run: mypy src tests
+
+      - name: Test (pytest)
+        run: pytest
+
+  integration:
+    # Without OEPT installed, the adapter/conformance tests skip silently and
+    # green CI proves nothing about OEVP+OEPT interop. This job installs OEPT
+    # and asserts the adapter is importable so the OEPT-dependent tests
+    # execute instead of skip.
+    name: OEPT integration (adapter + CLI + conformance enforced)
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+
+      - uses: actions/setup-python@v6
+        with:
+          python-version: "3.12"
+          cache: pip
+
+      - name: Install OEVP with dev tools
+        run: python -m pip install -e ".[dev]"
+
+      - name: Install OEPT (sibling repository, pinned snapshot)
+        # Bump to the latest OEPT tag/release when one is published to PyPI
+        # or tagged upstream.
+        run: python -m pip install "oept @ git+https://github.com/fintegra-ai/open-evidence-provenance.git@fec8f92ff98c2eaebb5c01ac178459f79c119e9b"
+
+      - name: Assert OEPT adapter is importable (no silent skips)
+        run: python -c "from oev.adapters.oept import is_oept_available; assert is_oept_available(), 'OEPT must be importable for this job'"
+
+      - name: Test (pytest, full suite with OEPT present)
+        run: pytest -rs

open_evidence_verification-0.2.1/.gitignore

@@ -0,0 +1,44 @@
+# 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/
+env/
+venv/
+ENV/
+
+# Tool caches
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+htmlcov/
+
+# IDE
+.vscode/
+.idea/
+*.swp
+*.swo
+*~
+.DS_Store

open_evidence_verification-0.2.1/CHANGELOG.md

@@ -0,0 +1,158 @@
+# Changelog
+
+All notable changes to the Open Evidence Verification Protocol (OEVP) will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+
+## [Unreleased]
+
+### Changed
+
+- Distribution name changed from `oev` to `open-evidence-verification` (PyPI name taken by an unrelated project). Import package `oev` and CLI `oev` are unchanged; install with `pip install open-evidence-verification[oept]` for the OEPT adapter.
+
+## [0.2.1] - 2026-11-01
+
+### Fixed
+
+- **Re-verification of a tampered receipt no longer reports `MATCH`.** When the
+  historical receipt's self-digest does not verify, `oev reverify` now fails
+  closed with `MISMATCH` (CLI exit code 2) instead of recording the failure in
+  `notes` and continuing — previously a receipt with an edited field (e.g. a
+  replaced `receipt_id`) and a stale `receipt_digest` could still produce
+  `MATCH` with exit code 0 if all other checks happened to agree.
+- CLI: schema-invalid or unparseable JSON inputs (e.g. a malformed receipt or
+  profile) now fail with a clean `Error: ...` message and exit code 1 instead
+  of an unhandled traceback.
+
+### Changed
+
+- The optional `oept` extra now depends on the `oept` distribution (OEPT's
+  actual PyPI/dist name), not the non-existent `open-evidence-provenance` name.
+- `oev reverify` human output and the README now state explicitly that
+  re-verification establishes reproducibility, not receipt authenticity;
+  `oev receipt verify` with caller-pinned verifier keys remains the
+  authenticity check.
+
+### Added
+
+- CI: a dedicated OEPT integration job that installs OEPT from the sibling
+  repository and asserts the adapter is importable, so the previously
+  auto-skipped adapter/CLI/conformance tests execute on every run.
+
+## [0.2.0] - 2026-10-26
+
+### Added
+
+- **Decision Evidence Pack** (`oev-decision-pack/0.2`): a portable, integrity-checked
+  directory format for the evidence trail of a decision process — case record, facts,
+  versioned rule runs (rules-as-data), findings, review actions, timeline, snapshot
+  context, and artifacts. Includes pack build, DSSE v1 manifest signing, and offline
+  integrity verification (`oev pack build|sign|verify`), a normative specification
+  (`spec/decision-pack-spec.md`), and a fully synthetic, domain-neutral example pack
+  (`examples/demo-case-001`, regenerable via `examples/make_example.py`).
+- **Portable pack verification receipt** (`oev-pack-receipt/0.1`,
+  `spec/decision-pack-spec.md` §7.1): `oev pack verify --out` emits a self-digested receipt
+  recording exactly which checks passed, failed, or were not run (the complete ordered check
+  vector), plus the declared and recomputed pack digest, the verifier identity/version, the
+  verification time, per-member results, and structure errors. The receipt can be DSSE-signed
+  (`--sign-receipt`) and is verifiable offline by a third party (`oev pack receipt verify`),
+  optionally bound against the pack on disk (`PACK_BINDING_MATCH` / `PACK_BINDING_MISMATCH`).
+  A receipt of an invalid pack is itself a valid record of that failure and never upgrades
+  the pack it describes. Schema: `pack-verification-receipt.schema.json`.
+- JSON schemas (Draft 2020-12) for the pack: `decision-pack-case`, `decision-pack-facts`,
+  `decision-pack-rule-runs`, `decision-pack-findings`, `decision-pack-review-actions`,
+  `decision-pack-timeline`, `decision-pack-snapshot-context`, and
+  `decision-pack-manifest`.
+- Conformance fixture `06-signature-invalid`: a corrupt application signature must
+  yield `FAIL` / `TECHNICAL_CHECKS_FAILED`, pinning the distinction from the
+  `UNVERIFIED` / `PROFILE_UNSATISFIED` outcome of an unsigned bundle (`03`).
+- Conformance fixtures `07`–`14` for the decision pack surface, derived deterministically
+  from the neutral `demo-case-001` example and runnable on the OEVP core alone (no OEPT):
+  replay OK on a pinned valid pack, `PACK_HASH_CHANGED` refusal of a self-consistent
+  rewrite, `SNAPSHOT_LEAK` refusal after late evidence injection, a third-party
+  pack-receipt round-trip (`RECEIPT_VALID` offline plus `PACK_BINDING_MATCH`), honest
+  `SIGNATURE_NOT_PRESENT` vs `SIGNATURE_INVALID` reporting, and archive refusals of
+  ZIP-slip traversal and duplicate member entries.
+- **Snapshot replay safety gate** (`oev.replay`, `oev pack replay`): replay of a pack's
+  snapshot now fails closed. Replay requires full pack verification first, refuses when the
+  pack hash changed since an out-of-band replay pin (`pin_pack`, `PACK_HASH_CHANGED` — this
+  catches fully self-consistent manifest rewrites that per-pack digests cannot), refuses when
+  caller-pinned trust roots are not satisfied by the manifest signature
+  (`SIGNATURE_UNTRUSTED`, covering stripping and replacement), and refuses when a recorded
+  rule run consumed evidence observed after the snapshot was captured (`SNAPSHOT_LEAK`).
+  The replay scope is computed by snapshot isolation: only facts bound to a snapshot source
+  and observed at or before `captured_at` are eligible; later or unbound evidence is excluded
+  with an explicit reason and can never enter a replay of that snapshot.
+- **Safe ZIP transport for packs** (`oev.pack_archive`): deterministic pack archive creation
+  and a validate-before-extract unpacker that rejects path-traversal entries (zip-slip),
+  duplicate member names, encrypted entries, and decompression bombs (per-entry and total
+  size bounds) — a hostile archive leaves the target directory untouched.
+- **Sabotage test suite** (`tests/test_sabotage.py`): 33 adversarial cases across byte flips
+  (members, artifacts, manifest, DSSE payload and signature bytes), ZIP traversal entries,
+  duplicate members (archive and manifest), signature stripping, signature replacement
+  (including keyid spoofing and envelopes over rewritten manifests), manifest tampering
+  (digest flips and self-consistent rebuilds), and replay with later evidence injected.
+- **Verifier-independence tests** (`tests/test_verifier_independence.py`): the offline
+  verifier's import closure is proven protocol-only (static AST and runtime `sys.modules`
+  checks; no application or store code), and the CLI verifier is exercised in a subprocess
+  against a pack copied to a clean directory containing no application code.
+- GitHub Actions CI running ruff, mypy (strict), and pytest on Python 3.10–3.13
+  (matching `requires-python`).
+- Schema-parity conformance guard: `schemas/` and the wheel-shipped `src/oev/schemas/`
+  copies must stay byte-identical.
+- `conformance/README.md` documenting the fixture corpus, expected results, and
+  regeneration procedure.
+
+### Changed
+
+- `oev pack verify` exit code `2` now also covers the case where the caller supplied
+  verifier trust roots but the pack carries no trusted manifest signature: a stripped
+  signature is a visible trust failure, never silent success (previously an unsigned pack
+  exited `0` even with keys supplied).
+- README rewritten to pro standard: what OEVP is and is not, trust boundaries in plain
+  language, and a quickstart where every command runs against the committed conformance
+  fixtures.
+- SECURITY.md expanded with report scope, supported versions, coordinated disclosure,
+  and an explicit "what verification does not protect against" section.
+- CONTRIBUTING.md and CODE_OF_CONDUCT.md completed (OEPT availability, quality gates,
+  full covenant structure).
+- Threat model (`spec/threat-model.md`) extended to the 0.2 decision pack surface: pack
+  member tampering, self-consistent manifest rewrites, signature stripping/replacement,
+  hostile pack archives, and snapshot replay leaks, with rule re-execution recorded as
+  an explicit non-goal.
+- Example pack `demo-case-001` regenerated so the committed bytes match the current
+  generator exactly: the DSSE envelope now embeds the signer's public key as an
+  unauthenticated hint (members, manifest, and pack digest are unchanged).
+- Receipts record the installed `oev` package version as the verifier identity version
+  (previously a hardcoded literal).
+- CLI exits with a clean error message (exit 1) instead of a traceback when the
+  optional OEPT adapter is missing.
+- Test suite no longer references paths outside the repository: OEPT-dependent tests use
+  the committed in-repo fixtures and skip with an explicit reason when OEPT is absent.
+
+### Removed
+
+- Dead code: `sha256_stream`/`sha256_file` (unused stream hashing helpers),
+  `get_available_adapters` (unused adapter registry accessor), `archive_info`
+  (unused archive summary helper), and the never-raised `PackVerifierError`.
+
+## [0.1.0] - Unreleased (draft)
+
+### Added
+
+- Initial pre-application MVP for the Open Evidence Verification Protocol.
+- JSON schemas: `verification-profile.schema.json`, `verification-receipt.schema.json`, `reverification-report.schema.json` (Draft 2020-12).
+- Deterministic RFC 8785 (JCS) canonicalization with integer range boundary enforcement `[-(2^53 - 1), 2^53 - 1]`.
+- Granular `CheckResult` model with 6 exact states: `PASS`, `FAIL`, `NOT_RUN`, `NOT_APPLICABLE`, `UNVERIFIED`, `UNSUPPORTED`.
+- Deterministic overall result aggregation with 5 exact states: `TECHNICAL_CHECKS_PASSED`, `TECHNICAL_CHECKS_FAILED`, `TECHNICAL_CHECKS_PARTIAL`, `EXECUTION_INCOMPLETE`, `PROFILE_UNSATISFIED`.
+- Canonical receipt digest with strict self-digest recursion avoidance rule.
+- DSSE v1 specification envelope implementation with PAE and Ed25519 signing.
+- Caller-supplied verifier trust roots preventing self-trust and key-hint impersonation.
+- Pluggable `PackageAdapter` protocol with optional reference `OEPTAdapter`.
+- Receipt inspection engine decoupled from package bytes.
+- Package re-verification engine comparing fresh evaluations against historical receipts.
+- Minimal CLI (`oev verify`, `oev inspect-receipt`, `oev reverify`, `oev receipt verify`).
+- Five primary MVP conformance fixtures.
+- Strict duplicate-key JSON rejection, input bounds, and profile check uniqueness hardening.

open_evidence_verification-0.2.1/CODE_OF_CONDUCT.md

@@ -0,0 +1,73 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Standards
+
+Examples of behavior that contributes to a positive environment include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from them
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement by opening a
+GitHub issue in this repository marked as a conduct report, or by contacting a
+maintainer privately through their GitHub profile. All complaints will be
+reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
+
+[homepage]: https://www.contributor-covenant.org

open_evidence_verification-0.2.1/CONTRIBUTING.md

@@ -0,0 +1,67 @@
+# Contributing to OEVP
+
+Thank you for contributing to the Open Evidence Verification Protocol.
+
+## Principles
+
+1. **Clean Codebase**: All contributions must be original work licensed under Apache-2.0.
+2. **Minimal Dependencies**: Runtime dependencies must remain strictly minimal (Python stdlib, `cryptography`, `jcs`, `jsonschema`).
+3. **Core Independence**: The protocol core (`src/oev` excluding `oev/adapters/oept.py`) must have zero imports or runtime dependencies on OEPT, EvidenceOS, or any financial software.
+4. **Deterministic Security**: All canonicalization, hashing, signature verification, and overall result aggregations must be fully deterministic and accompanied by tests.
+5. **Honest Boundaries**: Documentation and error messages must never claim factual truth, legal validity, compliance approval, or fraud detection. Verification is technical appraisal only (see [SECURITY.md](SECURITY.md)).
+6. **No Release Tags Pre-Review**: Pre-1.0 development proceeds under provisional specifications (`oev-profile/0.1`, `oev-receipt/0.1`, `oev-reverification/0.1`, `oev-decision-pack/0.2`).
+
+## Development setup
+
+```bash
+python3 -m venv .venv
+source .venv/bin/activate
+pip install -e ".[dev]"
+```
+
+Python ≥ 3.10 is supported (CI runs 3.10–3.13; see
+[.github/workflows/ci.yml](.github/workflows/ci.yml)).
+
+### Optional OEPT adapter
+
+The reference adapter for OEPT bundles is optional. The OEPT package (Open Evidence
+Provenance Toolkit) is a sibling project not yet published to PyPI; to run the
+OEPT-dependent tests and the full conformance suite locally, install OEPT from its own
+checkout:
+
+```bash
+pip install -e /path/to/open-evidence-provenance
+```
+
+Tests that require the adapter are skipped automatically (with an explicit reason) when
+OEPT is not installed; everything else — the whole protocol core, receipt inspection,
+and decision pack tooling — runs without it.
+
+## Quality gates
+
+Every pull request must pass (CI enforces the same checks on Python 3.10–3.13):
+
+```bash
+ruff check .
+ruff format --check .
+mypy src tests
+pytest
+```
+
+## Conformance fixtures
+
+The committed fixtures under [`conformance/fixtures`](conformance/fixtures) are the
+protocol's conformance corpus; [conformance/README.md](conformance/README.md) documents
+each scenario and how to regenerate them
+(`OEPT_FIXTURES_DIR=... python conformance/make_fixtures.py`).
+
+When changing verification behavior, keep the corpus consistent: fixtures and their
+`expected-result.json` files must reflect actual engine output, and every example in the
+[README](README.md) must run and verify against the code in this repository.
+
+## Pull requests
+
+- Keep changes focused; one logical change per PR.
+- Update [CHANGELOG.md](CHANGELOG.md) under `## [Unreleased]` for user-visible changes.
+- Update the spec documents under `spec/` in the same PR when protocol-level behavior
+  changes.

open_evidence_verification-0.2.1/LICENSE

@@ -0,0 +1,176 @@
+                                 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