modelferry 0.1.0__tar.gz

modelferry-0.1.0/.gitattributes

@@ -0,0 +1,5 @@
+# Normalize line endings to LF in the repo and on checkout. offline.py ships
+# verbatim into every bundle and its sha256 is recorded, so it must not vary by
+# platform. Keep all text files LF for determinism.
+* text=auto eol=lf
+*.py text eol=lf

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

@@ -0,0 +1,121 @@
+name: ci
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+concurrency:
+  group: ci-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+      # Fail if uv.lock does not match a default resolve of pyproject. This catches
+      # a lock accidentally left in --resolution lowest-direct mode by local floor
+      # experiments, so normal installs and CI keep resolving the highest versions.
+      - name: Lockfile is up to date
+        run: uv lock --check
+      - name: Sync dev environment
+        run: uv sync
+      - name: Ruff check
+        run: uv run ruff check .
+      - name: Ruff format check
+        run: uv run ruff format --check .
+      - name: Byte-compile offline.py on Python 3.9
+        run: uv run --no-project --python 3.9 python -m py_compile src/modelferry/offline.py
+
+  unit:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.10", "3.11", "3.12"]
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+      - name: Sync dev environment
+        run: uv sync --python ${{ matrix.python-version }}
+      - name: Unit tests (no network)
+        run: uv run pytest -m "not network"
+
+  # Resolve every direct dependency to its declared floor and run the suite, so
+  # the version lower bounds in pyproject are tested claims instead of Phase 1
+  # guesses. A floor that does not actually work turns this job red. The network
+  # integration test is included so the huggingface_hub floor (1.0.0) is exercised
+  # for real: the offline suite never imports huggingface_hub (hf.py's imports are
+  # lazy inside resolve_and_download), so only a real pack reaches it.
+  floor-test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+      - name: Sync at dependency floors
+        run: uv sync --resolution lowest-direct
+      - name: Offline tests at the floors
+        run: uv run pytest -m "not network"
+      - name: Integration test at the floors (network, exercises huggingface_hub 1.0.0)
+        run: uv run pytest -m network
+
+  integration:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+      - name: Sync dev environment
+        run: uv sync
+      - name: Integration tests (network, tiny public repo)
+        run: uv run pytest -m network
+
+  airgap-e2e:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+      - name: Sync dev environment
+        run: uv sync
+      - name: Air-gap end-to-end (docker, --network none)
+        run: bash scripts/e2e_airgap.sh
+
+  # Network job, like integration: install modelferry as a built wheel into a
+  # clean venv with the repo not on the path, then run the full pack/verify/unpack
+  # round trip from a temp dir. uv sync installs the project editable, so this is
+  # the only job that exercises the wheel a user actually gets, and it proves
+  # pack.py finds offline.py inside the installed package (not at a repo path).
+  wheel-install:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+      - name: Build the wheel
+        run: uv build
+      - name: Install the wheel into a clean venv (repo not on the path)
+        run: |
+          uv venv /tmp/wenv
+          uv pip install --python /tmp/wenv/bin/python dist/*.whl
+      - name: Pack/verify/unpack round trip from a temp dir (network, tiny repo)
+        env:
+          HF_HUB_DISABLE_PROGRESS_BARS: "1"
+        run: |
+          mf=/tmp/wenv/bin/modelferry
+          # Prove the CLI and its offline.py come from the installed wheel, not the
+          # repo checkout the reviewer worried could mask a __file__ resolution bug.
+          /tmp/wenv/bin/python -c "import modelferry,pathlib; p=pathlib.Path(modelferry.__file__); assert 'site-packages' in str(p), p; print('modelferry from', p)"
+          work="$(mktemp -d)"
+          cd "$work"
+          "$mf" pack hf-internal-testing/tiny-random-gpt2 --dest ./b --chunk-size 200K --exclude "*.bin" --exclude "*.h5"
+          bundle="$(echo ./b/tiny-random-gpt2__*)"
+          echo "bundle: $bundle"
+          "$mf" verify "$bundle"
+          "$mf" unpack "$bundle" ./out
+          test -f ./out/model.safetensors
+          echo "wheel-install round trip OK"

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

@@ -0,0 +1,134 @@
+name: release
+
+# Two independent triggers, so the TestPyPI rehearsal is a real rehearsal and a
+# re-run of the release tag can never be blocked by TestPyPI rejecting a
+# duplicate version:
+#
+#   workflow_dispatch  -> build and publish to TestPyPI. Run this manually from
+#                         the Actions tab before tagging, to rehearse the upload.
+#   push tag v*        -> build and publish to PyPI. This is the real release.
+#
+# Both publish steps use trusted publishing (OIDC), so no API tokens are stored
+# in the repo. Configure the publishers first:
+#   TestPyPI: https://test.pypi.org/manage/account/publishing/
+#   PyPI:     https://pypi.org/manage/account/publishing/
+# with owner HamzaAhmedWajeeh, repo modelferry, workflow release.yml, and the
+# environment names below (testpypi / pypi).
+
+on:
+  push:
+    tags:
+      - "v*"
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+      - name: Verify tag matches package version
+        if: startsWith(github.ref, 'refs/tags/v')
+        run: |
+          tag="${GITHUB_REF_NAME#v}"
+          pkg="$(uv run --no-project python -c 'import tomllib,pathlib; print(tomllib.loads(pathlib.Path("pyproject.toml").read_text())["project"]["version"])')"
+          echo "tag=$tag pkg=$pkg"
+          test "$tag" = "$pkg" || { echo "tag $tag does not match pyproject version $pkg"; exit 1; }
+      - name: Build sdist and wheel
+        run: uv build
+      - name: Check metadata
+        run: uvx twine check dist/*
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  # Manual rehearsal only (workflow_dispatch). Never runs on a tag push.
+  testpypi:
+    needs: build
+    if: github.event_name == 'workflow_dispatch'
+    runs-on: ubuntu-latest
+    environment: testpypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - name: Publish to TestPyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          repository-url: https://test.pypi.org/legacy/
+          # TestPyPI rejects duplicate versions; skip already-present files so a
+          # repeat rehearsal of the same version does not hard-fail. Not set on
+          # the PyPI job, where a duplicate should be a real error.
+          skip-existing: true
+
+  # Real release only (tag push). Runs BEFORE the PyPI publish (needs: build) so a
+  # failure here blocks the irreversible publish instead of following it: PyPI is a
+  # write-once index, a GitHub release is editable. Publishes the canonical sha256
+  # of the bundled verifier in the tag's release notes, the out-of-band mitigation
+  # the trust model (README, SPEC section 9) promises: a receiving site can check a
+  # bundle's tools/modelferry_offline.py against this hash before trusting it, or
+  # bring its own known-good copy. Idempotent, so a re-run after a later-step
+  # failure edits the existing release instead of erroring on "already exists".
+  github-release:
+    needs: build
+    if: startsWith(github.ref, 'refs/tags/v')
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/checkout@v4
+      - name: Create the GitHub release with the canonical offline.py hash
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: |
+          sha="$(sha256sum src/modelferry/offline.py | cut -d' ' -f1)"
+          # Lead with the CHANGELOG 0.1.0 section so the release page says what this
+          # is, then append the verifier block. The awk prints from the 0.1.0 header
+          # up to (not including) the link-reference lines at the end of the file.
+          awk '/^## \[0\.1\.0\]/{f=1} f && /^\[.*\]: /{exit} f{print}' CHANGELOG.md > notes.md
+          cat >> notes.md <<EOF
+
+          ## Verifier
+
+          Canonical sha256 of the offline verifier, copied verbatim into every bundle
+          at \`tools/modelferry_offline.py\` and recorded as \`verifier.sha256\` in each
+          \`manifest.json\`:
+
+          \`\`\`
+          $sha  offline.py
+          \`\`\`
+
+          A receiving site can check a bundle's verifier against this hash out-of-band
+          before trusting it, or ignore the bundled copy and bring its own known-good
+          verifier. See the trust model in the README.
+          EOF
+          if gh release view "$GITHUB_REF_NAME" >/dev/null 2>&1; then
+            gh release edit "$GITHUB_REF_NAME" --notes-file notes.md
+          else
+            gh release create "$GITHUB_REF_NAME" --title "$GITHUB_REF_NAME" --notes-file notes.md
+          fi
+
+  # Real release only (tag push), gated on github-release so the write-once PyPI
+  # publish happens last, only after the release-notes step has succeeded.
+  pypi:
+    needs: github-release
+    if: startsWith(github.ref, 'refs/tags/v')
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

modelferry-0.1.0/.gitignore

@@ -0,0 +1,33 @@
+# Byte-compiled / optimized
+__pycache__/
+*.py[cod]
+*.pyo
+
+# Virtual environments
+.venv/
+venv/
+
+# Tool caches
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+
+# Build / packaging artifacts
+build/
+dist/
+*.egg-info/
+
+# Coverage
+.coverage
+htmlcov/
+
+# OS cruft
+.DS_Store
+
+# Local Claude Code state (personal, not shared)
+.claude/
+
+# Local demo / scratch bundles (e.g. the README quickstart's --dest ./bundles)
+/bundles/
+/tmp_snapshot/
+/make_demo_bundle.py

modelferry-0.1.0/CHANGELOG.md

@@ -0,0 +1,53 @@
+# Changelog
+
+All notable changes to modelferry are recorded here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and versions follow
+[Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.1.0] - 2026-07-16
+
+First release.
+
+### Added
+
+- `modelferry pack REPO_ID --dest DIR`: download a Hugging Face model repo pinned
+  to a commit, split oversized files into `.mfpartNNNN` parts, hash everything
+  with sha256, and write a bundle with `manifest.json`, `MANIFEST.md`, the
+  payload, and a copy of the offline verifier.
+- `modelferry verify`, `unpack`, and `inspect`: thin wrappers over the exact
+  standard-library verifier that ships inside every bundle, so the installed CLI
+  and the bundled tool behave identically.
+- `src/modelferry/offline.py`: the self-contained verifier and unpacker. Standard
+  library only, runs on CPython 3.9, no network, no third-party packages. Copied
+  verbatim into every bundle at `tools/modelferry_offline.py`.
+- `manifest.json` (version 1): deterministic, `sort_keys` serialization with
+  whole-file and per-part sha256 hashes, source repo and resolved commit SHA,
+  license, gated flag, and the verifier hash.
+- `MANIFEST.md`: human-readable approval document for security review.
+- Chunking sized for FAT32 by default (`--chunk-size 3900M`), with `--include` /
+  `--exclude` fnmatch filtering and resumable downloads via `--staging`.
+- Streamed IO with a fixed 8 MiB buffer throughout, so bundles larger than RAM
+  pack and verify with flat memory use.
+- Zip-slip-safe unpack: absolute paths, `..` segments, and anything resolving
+  outside the destination are rejected, and symlinks are never created.
+- Post-pack read-back self-verify, so disk-level write errors surface before the
+  bundle leaves the connected side.
+- Exit codes per SPEC section 10 (0 success, 1 integrity, 2 usage, 3 source,
+  4 filesystem).
+
+### Security
+
+- `HF_TOKEN` is read from the environment only and is never written into a
+  bundle, manifest, receipt, or log. A test packs with a fake token and asserts
+  the token bytes appear nowhere in the output.
+- The trust model is documented in the README. v1 covers accidental corruption,
+  incomplete transfers, media errors, and casual tampering. It does not cover a
+  coordinated adversary who rewrites payload, manifest, and verifier together;
+  that needs out-of-band signature verification, planned for v1.1. Each release
+  publishes the canonical `offline.py` sha256 so a receiving site can check the
+  bundled verifier out-of-band.
+
+[Unreleased]: https://github.com/HamzaAhmedWajeeh/modelferry/compare/v0.1.0...HEAD
+[0.1.0]: https://github.com/HamzaAhmedWajeeh/modelferry/releases/tag/v0.1.0

modelferry-0.1.0/CLAUDE.md

@@ -0,0 +1,34 @@
+# modelferry
+
+CLI that packs Hugging Face models into chunked, sha256-manifested bundles for transfer into air-gapped environments, and verifies/unpacks them offline. SPEC.md is the contract: read the relevant sections before implementing anything. If the spec turns out to be wrong or ambiguous, stop and ask; when we agree on a change, update SPEC.md in the same commit as the code.
+
+## Commands
+
+- Setup: `uv sync`
+- Tests (default, no network): `uv run pytest -m "not network"`
+- All tests: `uv run pytest`
+- Lint + format: `uv run ruff check . && uv run ruff format .`
+- Air-gap end-to-end (needs docker): `bash scripts/e2e_airgap.sh`
+
+## Hard rules
+
+- IMPORTANT: `src/modelferry/offline.py` uses the Python standard library only, runs on CPython 3.9, imports nothing from the modelferry package, and stays under ~550 lines (raised from 500 in phase 2.2 to fit symlink/atomic-join/part-name hardening). It is copied verbatim into every bundle. The AST test in tests/ enforces this; never loosen that test.
+- IMPORTANT: never write tokens or secrets into bundles, manifests, receipts, or logs. `HF_TOKEN` is read from the environment only.
+- manifest.json format is frozen once Phase 2 merges. Any structural or semantic change bumps `manifest_version` and updates SPEC.md §5 in the same commit.
+- All payload IO is streamed with a fixed 8 MiB buffer. Never read a payload file fully into memory.
+- Unpack rejects absolute paths, `..` segments, and anything resolving outside the destination. Never create symlinks.
+- Exit codes exactly per SPEC.md §10. Do not invent new ones.
+- Runtime dependencies are typer, rich, huggingface_hub. Do not add a fourth without asking.
+- Never weaken a corruption, path-safety, or token-leak test to make it pass. Fix the code instead.
+- Every bugfix ships with a regression test.
+
+## Workflow
+
+- Build in the phase order of SPEC.md §13, one phase per session.
+- Mark network-dependent tests `@pytest.mark.network` so the default test run stays offline.
+- Before declaring a phase done: ruff clean, `pytest -m "not network"` green, and for Phase 4+ the e2e script passes.
+- Commit at phase boundaries with short imperative messages (e.g. "phase 2: offline verifier + tests").
+
+## Prose style (README, MANIFEST.md template, all docs)
+
+- Plain sentences, contractions, no em dashes, no marketing adjectives, no bullet-point walls. Write like an engineer explaining to another engineer.

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