keyfleet 0.1.0__tar.gz

keyfleet-0.1.0/.gitattributes

@@ -0,0 +1,4 @@
+# Owner works on Windows and macOS: normalize to LF in the repo.
+* text=auto eol=lf
+*.png binary
+*.gif binary

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

@@ -0,0 +1,28 @@
+name: ci
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test:
+    name: test (${{ matrix.os }})
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, windows-latest, macos-latest]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v10.0.1
+        with:
+          python-version: "3.12"
+      # Exercise the age round-trip tests on at least one OS (they skip
+      # gracefully where the binary is absent).
+      - if: runner.os == 'Linux'
+        run: sudo apt-get update && sudo apt-get install -y age
+      - run: uv sync --all-extras --dev
+      - run: uv run ruff check .
+      - run: uv run ruff format --check .
+      - run: uv run pytest -q

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

@@ -0,0 +1,38 @@
+name: release
+
+# Publishes to PyPI via trusted publishing (OIDC, no stored token) when a
+# v* tag is pushed. PyPI-side publisher config: owner ThePrimeLayer,
+# repo keyfleet, workflow release.yml, environment pypi.
+
+on:
+  push:
+    tags: ["v*"]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v10.0.1
+        with:
+          python-version: "3.12"
+      - run: uv build
+      - uses: actions/upload-artifact@v7
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/project/keyfleet/
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v8
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1

keyfleet-0.1.0/.gitignore

@@ -0,0 +1,16 @@
+# keyfleet — never commit a real ledger (AGENTS.md §8.3).
+# Only the fictional keyfleet.example.yaml is committed.
+keyfleet.yaml
+keyfleet.yml
+
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+.venv/
+build/
+dist/
+.pytest_cache/
+.ruff_cache/
+.coverage
+htmlcov/

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

@@ -0,0 +1,14 @@
+# ruff and gitleaks are pinned to exact versions on purpose (AGENTS.md §8.5).
+# The ruff rev must match the ruff pin in pyproject.toml [dependency-groups].
+# Bump either only in a dedicated `chore(deps):` commit.
+repos:
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.16.5
+    hooks:
+      - id: ruff-check
+        args: [--fix]
+      - id: ruff-format
+  - repo: https://github.com/gitleaks/gitleaks
+    rev: v8.30.1
+    hooks:
+      - id: gitleaks

keyfleet-0.1.0/.python-version

@@ -0,0 +1 @@
+3.12

keyfleet-0.1.0/AGENTS.md

@@ -0,0 +1,100 @@
+# AGENTS.md — keyfleet
+
+Instructions for any coding agent working in this repository (Codex, Cursor, Copilot, Cline/Kilo, Claude Code via `CLAUDE.md`). Explicit instructions from the user override this file. This file is the single source of truth for **how to work here**; `keyfleet-BRIEF.md` is the source of truth for **what to build**. If they conflict on scope, the brief wins; on process, this file wins.
+
+## 1. What this project is
+
+`keyfleet` is a local-first Python CLI that keeps a YAML ledger of hardware security keys ↔ accounts ↔ credential types and reports coverage gaps, lost-key impact, capacity, and advisories. It stores **no secrets** and makes **no network calls**. Full specification: `keyfleet-BRIEF.md` — read it completely before your first change, then consult it by section (§7 data model, §8 CLI, §9 logic, §15 open decisions).
+
+## 2. Session start (every session, every harness)
+
+1. If `PLAN.md` exists, read it first: milestones, open questions, and the session log tell you where the last agent stopped. If it does not exist, read the brief and create `PLAN.md` per brief §16.
+2. Run `git status` and `git log --oneline -15` to orient.
+3. Work in small steps. Before ending, append a session-log line to `PLAN.md` (format in §9).
+
+## 3. Commands
+
+| Task | Command |
+|---|---|
+| Set up environment | `uv sync --all-extras --dev` |
+| Run the CLI | `uv run keyfleet --help` |
+| Tests (all / one file) | `uv run pytest -q` / `uv run pytest tests/test_checks.py -q` |
+| Lint + format | `uv run ruff check . && uv run ruff format .` |
+| All hooks | `uv run pre-commit run --all-files` |
+| Build wheel | `uv build` |
+
+Always prefix with `uv run`. Never `pip install` into a global/system Python. Commands are identical in PowerShell on Windows; write cross-platform code (`pathlib`, no shell one-liners in library code).
+
+## 4. Repository map
+
+```
+src/keyfleet/          cli.py (typer) · model.py (pydantic) · checks.py, impact.py (pure functions) · report.py (rich/markdown/json) · crypto.py (optional age decryption) · data/{models,services,advisories}.yaml
+schema/                keyfleet.schema.json (generated from the pydantic models; regenerate when model.py changes)
+tests/                 fixtures/*.yaml · one test module per check · data-integrity tests
+docs/                  ASSUMPTIONS.md (unverified facts) · DECISIONS.md (choices + rationale) · SERVICES.md (generated)
+keyfleet.example.yaml  fictional example ledger; the only ledger ever committed
+PLAN.md                milestones, open questions, session log
+CHANGELOG.md           Keep a Changelog format; add to "Unreleased" as you go
+```
+
+## 5. Code conventions
+
+- Python 3.12+, full type hints, `pydantic` v2 models in `model.py`, `typer` CLI in `cli.py`, `rich` for terminal output, `yaml.safe_load` only.
+- `checks.py` and `impact.py` are **pure**: they take the loaded ledger model and return findings; no file or terminal I/O inside them.
+- Exit codes: `0` clean, `1` findings at FAIL level, `2` tool/usage error. Every finding carries an actionable message and, where possible, a link from `services.yaml`.
+- Errors for bad ledgers must say *which file, which key/account id, which field* and how to fix it.
+- Use `logging`, not `print`, outside the report layer. No global mutable state.
+- Keep modules under ~400 lines; split by responsibility, not by size.
+- Do not add a dependency without a line in `docs/DECISIONS.md` (what, why, alternative considered).
+
+## 6. Data files (`src/keyfleet/data/*.yaml`)
+
+- Every entry has `source_url` and `verified: YYYY-MM-DD`. If a fact cannot be verified on the vendor's or service's own page, write `null` — never guess.
+- `models.yaml`: capabilities, interfaces, discoverable-credential capacity per model/firmware.
+- `services.yaml`: security-settings URL, max keys allowed, discoverable-credential support. Keep entries alphabetical by id.
+- `advisories.yaml`: vendor advisories with `affects` rules (firmware ranges). Summaries in your own words; link the advisory.
+- Data-integrity tests must pass after any edit (unique ids, valid URL syntax, ints or null for capacities). Regenerate `docs/SERVICES.md` when `services.yaml` changes.
+
+## 7. Testing
+
+- `pytest`; fixtures under `tests/fixtures/`; one module per check with positive and negative cases; golden files for `check`/`report` output.
+- Tests never touch the network and never depend on the `age` binary (skip that test when it is absent).
+- Must pass on Linux, macOS, and Windows (CI runs all three): use `tmp_path`, `pathlib`, UTF-8 explicitly.
+- Add or update tests in the same commit as the behavior change. Target ≥85% coverage on `checks.py` and `impact.py`.
+
+## 8. Security and privacy invariants (non-negotiable)
+
+1. **No network calls in runtime code.** A test greps `src/` for `httpx`, `requests`, `urllib`, `socket`, `aiohttp` and fails on any import.
+2. **No secrets in the ledger.** Validation rejects fields or values that look like recovery codes, TOTP seeds, PINs, or OTP secrets, with a clear message. Tests cover this.
+3. **Never commit a real ledger.** `keyfleet.yaml` and `*.age` decrypted output are gitignored; only `keyfleet.example.yaml` (fictional) is committed.
+4. **No telemetry, ever.**
+5. **Supply chain:** `.pre-commit-config.yaml` pins `ruff` and `gitleaks` to exact versions; do not change pins except in a dedicated `chore(deps):` commit.
+6. If a request would violate any of the above, stop and say so instead of complying.
+
+## 9. Workflow and git
+
+- Conventional commits: `feat:`, `fix:`, `test:`, `docs:`, `chore:`, `refactor:`. One logical change per commit; run `ruff` and `pytest` before committing.
+- Small changes go directly on `main`. Anything that changes the ledger schema, a data-file format, or the CLI surface goes on a `feat/<topic>` branch with a short PR description (even if the owner merges it alone).
+- Never force-push `main` or rewrite published history.
+- `CHANGELOG.md`: add a bullet under **Unreleased** in the same commit as a user-visible change.
+- `docs/ASSUMPTIONS.md`: record every external fact you relied on but could not verify (vendor capacities, service limits, API details) with a date and a link.
+- `docs/DECISIONS.md`: one short entry per non-obvious choice (dependency, schema shape, threshold): context → decision → alternatives.
+- **No churn.** Do not reformat, rename, or reorganize files that the task does not require. Do not rewrite `PLAN.md` milestones or the brief; propose changes in chat and edit only after agreement.
+- Session log (append to the end of `PLAN.md`):
+  `- 2026-08-29 · <harness> · <what changed, 1 line> · next: <1 line> · open: <question or "none">`
+
+## 10. Decisions that require the owner
+
+From brief §15: license (Apache-2.0 recommended), default policy numbers (`T0: 3, T1: 2, T2: 1`), and the package/repo name if `keyfleet` is taken on PyPI/GitHub. Ask these **once, in a single batched message**, propose a default for each, and continue with the recommended default on anything non-blocking. Record the answers in `docs/DECISIONS.md`. Do not ask questions the brief or this file already answers.
+
+## 11. Definition of done for v0.1.0
+
+Everything in brief §4 shipped; CI green on all three OSes; the README quick start executed literally from a clean clone; `CHANGELOG.md` entry; git tag `v0.1.0`; `uv build` succeeds. When a milestone or the release is complete, report: what shipped, what is assumed (link `docs/ASSUMPTIONS.md`), what is next.
+
+## 12. Harness notes
+
+- **Claude Code** reads `CLAUDE.md`, which imports this file. Put shared rules here, not there.
+- **Codex** reads this file directly (keep it under the 32 KiB cap; no `AGENTS.override.md` is used in this repo).
+- **Cursor** reads `AGENTS.md` natively; add `.cursor/rules/*.mdc` only for glob-scoped extras, never for rules that belong here.
+- **GitHub Copilot** reads `AGENTS.md`; no separate `copilot-instructions.md` is maintained.
+- **Other harnesses** that do not discover `AGENTS.md`: point their rules file at this one (a one-line "Read and follow AGENTS.md" is enough). Do not fork the content.

keyfleet-0.1.0/CHANGELOG.md

@@ -0,0 +1,61 @@
+# Changelog
+
+All notable, user-visible changes to keyfleet are documented in this file.
+
+Format: [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) ·
+versioning: [SemVer](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.1.0] - 2026-08-30
+
+First release: the ledger, the checker, the incident tooling, and the
+source-cited services dataset.
+
+### Added
+
+- YAML ledger schema (keys ↔ accounts ↔ registrations, policy, advisories)
+  with strict validation, referential-integrity checks, and errors that name
+  the file, the offending key/account id, and the field.
+- Secret rejection: a ledger containing anything that looks like a recovery
+  code, TOTP seed, PIN, or OTP secret (by field name or value shape) is
+  refused with an explanation — keyfleet stores pointers, never secrets.
+- `keyfleet validate [LEDGER]` — exit 0 valid, 1 invalid, 2 missing file.
+- Published JSON Schema at `schema/keyfleet.schema.json` for editor
+  completion, generated from the models.
+- Fictional example ledger `keyfleet.example.yaml`.
+- `keyfleet check [LEDGER] [--json]` with the min-keys coverage rule: FAIL for
+  every account holding fewer active/spare keys than `policy.min_keys[tier]`
+  (defaults T0:3, T1:2, T2:1); lost/retired keys never count. Exit 1 when any
+  FAIL finding exists.
+- Lost/retired hygiene check: FAIL for every lost or retired key that is still
+  registered on any account, pointing at `keyfleet lost KEY` for the
+  de-registration checklist.
+- Weak-factor check: WARN for every factor a tier's policy warns against
+  (default: sms and email on T0 accounts).
+- Unregistered-spare check: WARN for spare keys registered on no account.
+- Recovery-code pointer check: INFO for accounts in tiers listed in
+  `policy.require_recovery_codes_for` (default T0+T1) that have no stored
+  recovery-code pointer.
+- Encrypted ledgers: every command transparently reads `keyfleet.yaml.age`
+  (or any `*.age` path) via the `age` CLI, decrypting to memory only; set
+  `KEYFLEET_AGE_IDENTITY` to an identity file for non-interactive use.
+- `keyfleet init` — writes the fictional example ledger into the current
+  directory and makes sure `.gitignore` covers `keyfleet.yaml`.
+- `keyfleet advisories` — matches every key against the bundled advisory list
+  (plus any ledger-local advisories) by vendor and firmware range; keys
+  without `firmware:` are prompted to set it.
+- `keyfleet services [--search NAME]` — prints the bundled service table.
+- `keyfleet report [--md|--json]` — coverage matrix (accounts x keys with
+  registration types), per-tier summary, and key utilization including
+  discoverable-credential usage against known capacities.
+- `keyfleet lost KEY_ID [--md]` — lost-key impact analysis and an ordered
+  de-registration checklist (tier first, becomes-inaccessible first) with the
+  registration nicknames to delete and each service's security-settings URL.
+- Bundled reference data, every fact verified on the vendor's own page (or
+  `null`, never guessed): `services.yaml` with 32 services (settings URLs,
+  documented key limits, passkey support), `models.yaml` with
+  discoverable-credential capacities per firmware (YubiKey 5 / Security Key
+  series 25→100 at 5.7, Nitrokey 3 family), and `advisories.yaml` seeded with
+  YSA-2024-02, YSA-2024-03, and YSA-2025-02. `docs/SERVICES.md` is generated
+  from the services table.

keyfleet-0.1.0/CLAUDE.md

@@ -0,0 +1,34 @@
+# keyfleet — Claude Code
+
+@AGENTS.md
+
+Shared rules live in `AGENTS.md` (imported above). This file adds only what is specific to working with Claude Code. Keep it under 60 lines; if a rule applies to every harness, move it to `AGENTS.md`.
+
+## Orientation
+
+- Start from `PLAN.md`. If it is missing, read `keyfleet-BRIEF.md` in full and create `PLAN.md` per the brief's §16 before touching code.
+- The brief is deliberately **not** imported here: imports load on every launch, and the brief is only needed when a task touches something it specifies (schema, CLI surface, a check's logic, data files). Open the relevant section at that point.
+
+## Working style
+
+- When a decision needs the owner, present it as a short numbered fork with a recommended default, batch all such questions into one message, and keep working on unblocked tasks. No "shall I continue?" check-ins; end the turn when the requested slice is done or you are blocked.
+- Push back plainly when the brief, `PLAN.md`, or a request is wrong or would breach an invariant in `AGENTS.md` §8 — before doing it, not after.
+- Use plan mode (or a ≤10-line plan in chat) for anything that changes the ledger schema, a data-file format, or the CLI surface. Skip the plan for single-check or single-test changes.
+- Do not rewrite `PLAN.md` milestones or the brief on your own; propose in chat, edit after agreement.
+
+## Tooling
+
+- `uv run …` for every Python invocation; never call `pip`, `python -m pip`, or a global interpreter.
+- The owner works on both Windows (PowerShell) and macOS: prefer commands that are identical on both; use `pathlib` in code and in test helpers.
+- When you need a fact about a key vendor, a service's security-key settings, or an advisory, read the vendor's/service's own page and record the URL and date in the data file (`source_url`, `verified`) or in `docs/ASSUMPTIONS.md`. Never fill a data entry from memory.
+
+## Finishing a task or milestone
+
+1. `uv run ruff check . && uv run ruff format . && uv run pytest -q`
+2. Update `CHANGELOG.md` (Unreleased) for user-visible changes and append the session-log line to `PLAN.md`.
+3. Summarize: shipped / assumed / next.
+
+## Don'ts
+
+- Don't add dependencies silently, touch the `gitleaks` or `ruff` pins outside a `chore(deps):` commit, add network calls, or commit `keyfleet.yaml`.
+- Don't reformat or reorganize files the task doesn't require.

keyfleet-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,75 @@
+# Contributing to keyfleet
+
+Thanks for helping! The most valuable contribution by far is a **service
+entry** — it takes ten minutes and makes `keyfleet lost` and `keyfleet check`
+smarter for everyone.
+
+## Add a service (the ten-minute PR)
+
+1. Open the service's **own** documentation/help page about security keys or
+   passkeys. Facts must come from a page on the vendor's domain — that page
+   becomes `source_url`. No blog posts, no memory, no guessing.
+2. Add an entry to [`src/keyfleet/data/services.yaml`](src/keyfleet/data/services.yaml),
+   **alphabetical by id**:
+
+   ```yaml
+   example:
+     name: "Example"
+     security_settings_url: https://example.com/settings/security  # only if documented/linked; else null
+     max_keys: null              # integer only if the page states a limit
+     fido2_discoverable: true    # passkeys supported? true / false / null (page doesn't say)
+     notes: "One short sentence from the page, in your own words."
+     source_url: https://help.example.com/security-keys
+     verified: 2026-08-30        # the day YOU read the page
+   ```
+
+   `null` never means "probably not" — it means *the page does not say*.
+   A service with **no** security-key support at all is still a great entry:
+   set `fido2_discoverable: false` and say so in `notes` (see `steam`).
+3. Regenerate the table and run the data tests:
+
+   ```bash
+   uv run python scripts/gen_services_md.py
+   ```
+
+   ```bash
+   uv run pytest tests/test_data_files.py -q
+   ```
+
+4. Commit as `data(services): add example`, one service per PR, and paste the
+   sentence from the vendor page that supports each non-null fact into the PR
+   description.
+
+Corrections use the same rules — update `verified` to the day you re-checked.
+`models.yaml` (key capabilities/capacities) and `advisories.yaml` (vendor
+advisories with firmware ranges) follow the same source-cited pattern; see the
+header comments in each file.
+
+## Code contributions
+
+```bash
+uv sync --all-extras --dev
+```
+
+```bash
+uv run pytest -q
+```
+
+```bash
+uv run pre-commit run --all-files
+```
+
+- Conventional commits (`feat:`, `fix:`, `test:`, `docs:`, `data:`, `chore:`);
+  one logical change per commit; tests land in the same commit as the change.
+- `checks.py` and `impact.py` stay pure (no I/O); rendering lives in
+  `report.py`; every finding must tell the user what to *do*.
+- Two hard rules, enforced by tests, not negotiable: **no network calls in
+  runtime code** and **no storing secrets** (the validator must keep refusing
+  anything that looks like one).
+- After changing `model.py`, regenerate the JSON schema:
+  `uv run python scripts/gen_schema.py`. After changing CLI output on
+  purpose, regenerate goldens: `KEYFLEET_UPDATE_GOLDENS=1 uv run pytest -q`
+  and review the diff.
+
+Agent-assisted contributions are welcome; the repo's ground rules for that
+live in [AGENTS.md](AGENTS.md).

keyfleet-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.