adk-code-mode 0.1.0__py3-none-any.whl

adk_code_mode-0.1.0.dist-info/METADATA

@@ -0,0 +1,351 @@
+Metadata-Version: 2.4
+Name: adk-code-mode
+Version: 0.1.0
+Summary: A "Code Mode" Code Executor for ADK for agents to interact with tools, files, and custom packages with Python
+Project-URL: Documentation, https://github.com/A2ANet/adk-code-mode#readme
+Project-URL: Issues, https://github.com/A2ANet/adk-code-mode/issues
+Project-URL: Source, https://github.com/A2ANet/adk-code-mode
+Author-email: A2A Net <hello@a2anet.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: a2a,adk,agents,code-executor,code-mode
+Classifier: Development Status :: 4 - Beta
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: Implementation :: CPython
+Requires-Python: >=3.10
+Requires-Dist: docker>=7.0.0
+Requires-Dist: google-adk<2.0.0,>=1.0.0
+Requires-Dist: google-genai>=1.0.0
+Requires-Dist: pydantic>=2.0.0
+Description-Content-Type: text/markdown
+
+# ADK Code Mode
+
+A [Code Mode](https://blog.cloudflare.com/code-mode/) code executor for [Agent Development Kit (ADK)](https://github.com/google/adk-python).
+The `CodeModeCodeExecutor` allows ADK to write Python code to call tools and list, save, and load Artifacts.
+
+The code is executed in a Docker container, tool calls are forwarded to the host, and are run through ADK's normal tool pipeline (callbacks, plugins, error handling).
+The default Docker image supports The Python Standard Library, extra Python packages can be added by building a custom Docker image.
+Files can be added to a single execution with `input_files`, and saved files are output as `output_files`.
+By default, `CodeModeCodeExecutor` adds `list_artifacts`, `save_artifact`, and `load_artifact` tools to the execution environment to use files between executions.
+
+Inspired by Cloudflare's [Code Mode](https://blog.cloudflare.com/code-mode/) and Anthropic's [Code execution with MCP](https://www.anthropic.com/engineering/code-execution-with-mcp).
+
+## ✨ Features
+
+- **Call ADK tools from sandbox code** — imports against the `tools` package proxy back to the host and run through ADK's `before_tool` / `after_tool` / `on_error` callbacks and the plugin manager exactly as direct tool calls would.
+- **Credentials stay on the host** — API keys, OAuth tokens, and connection strings never enter the container; only tool arguments and return values cross the boundary.
+- **Bake any Python package into the image** — extend the published base image with anything the model's code needs to `import`, no runtime `pip install` required.
+- **Cross-turn persistence via ADK Artifacts** — `save_artifact` / `load_artifact` / `list_artifacts` are auto-injected and route through your configured `ArtifactService`.
+- **Bounded stdout/stderr** — overflow lands in a session artifact instead of poisoning the prompt.
+- **Local development** — `DockerRuntime` runs the sandbox against your local Docker daemon for fast iteration.
+
+|                                     | BuiltIn | AgentEngineSandbox              | VertexAi                        | Container | Gke | CodeMode                 |
+| ----------------------------------- | ------- | -------------------------------- | ------------------------------- | --------- | --- | ------------------------ |
+| Call ADK tools from code            | no                  | no                              | no                              | no                    | no              | yes (with limitations)   |
+| Extra Python packages               | no                  | no (more than stdlib but fixed) | no (more than stdlib but fixed) | yes                   | yes             | yes                      |
+| Variables are stateful              | no                  | yes                             | yes                             | no                    | no              | no                       |
+| Input files                         | no                  | yes                             | yes                             | no                    | no              | yes                      |
+| Output files                        | no                  | yes                             | yes                             | no                    | no              | yes                      |
+| Storage                             | no                  | yes (via variables)             | yes (via variables)             | no                    | no              | yes (via ADK Artifacts)  |
+| Local development version available | no                  | no                              | no                              | yes                   | yes             | yes                      |
+| Bounded stdout/stderr               | no                  | no                              | no                              | no                    | no              | yes (`max_output_chars`) |
+
+## 📋 Requirements
+
+- Python 3.10+
+- [Docker](https://docs.docker.com/get-docker/) — `DockerRuntime` launches the sandbox via the local Docker daemon, so the agent process needs to reach a Docker socket.
+- (optional) [uv](https://docs.astral.sh/uv/) if you prefer it over pip.
+
+## 📦 Install
+
+```bash
+pip install adk-code-mode
+```
+
+Or with uv:
+
+```bash
+uv add adk-code-mode
+```
+
+## 🚀 Usage
+
+Build a `CodeModeCodeExecutor`, wire `code_mode_before_model_callback` into the agent, and put `CODE_MODE_SYSTEM_INSTRUCTION` somewhere in the agent's `instruction`:
+
+```python
+from google.adk.agents import LlmAgent
+from adk_code_mode import (
+    CODE_MODE_SYSTEM_INSTRUCTION,
+    CodeModeCodeExecutor,
+    DockerRuntime,
+    code_mode_before_model_callback,
+)
+
+executor = CodeModeCodeExecutor(
+    tools=[my_fn_tool, McpToolset(...), OpenAPIToolset(...)],
+    runtime=DockerRuntime(image="ghcr.io/a2anet/adk-code-mode:0.1.0"),
+)
+
+root_agent = LlmAgent(
+    name="assistant",
+    model="gemini-2.5-pro",
+    instruction=f"You are a helpful assistant.\n\n{CODE_MODE_SYSTEM_INSTRUCTION}",
+    tools=[],  # do NOT also bind tools here; the executor owns them.
+    code_executor=executor,
+    before_model_callback=code_mode_before_model_callback(executor),
+)
+```
+
+The callback is what injects the tool catalog. Skip it and the model has no idea what tools exist.
+
+Inside the sandbox, the model writes code like:
+
+```python
+from tools.slack import send_message
+print(send_message(channel="C123", text="hi"))
+```
+
+## 🗂️ Storage
+
+Code Mode exposes two separate file surfaces:
+
+- **`/workspace`** — per-run working directory for ordinary I/O.
+- **ADK Artifacts** — persistent, cross-turn files and data via `save_artifact` / `load_artifact` / `list_artifacts`.
+
+### `/workspace`
+
+`/workspace` is the sandbox's current working directory for a single execution. Any ADK `input_files` are staged there by filename before the code runs, so plain paths like `open("input.csv")` work.
+
+Files created or modified under `/workspace` are returned as `CodeExecutionResult.output_files` at the end of the run — these are developer-internal, intended for things like staged inputs or generated reports a downstream tool consumes. They are not re-hydrated next turn unless the code explicitly persists them via `save_artifact`.
+
+### Artifacts
+
+`CodeModeCodeExecutor` injects three regular tools into the catalog so model code can persist files across turns. They appear as top-level `from tools import …` imports:
+
+```python
+import json
+from tools import save_artifact, load_artifact, list_artifacts
+
+save_artifact(
+    filename="report.json",
+    content=json.dumps({"status": "ready"}),
+    mime_type="application/json",
+)
+print(list_artifacts())
+report = load_artifact(filename="report.json")
+if report is not None and report["kind"] == "text":
+    payload = json.loads(report["data"])
+```
+
+To opt out and supply your own artifact tools (or none), pass `include_artifact_tools=False`.
+
+To react when the model saves an artifact (for example to surface it as an A2A artifact-update event), pass `on_artifacts_saved`:
+
+```python
+async def on_saved(invocation_context, delta):
+    # ``delta`` is ``{filename: version}`` for everything saved this turn.
+    ...
+
+CodeModeCodeExecutor(tools=..., runtime=..., on_artifacts_saved=on_saved)
+```
+
+The hook fires once per `execute_code` call, after the sandbox closes, only when the dispatcher recorded at least one save. Exceptions raised inside the hook are logged and swallowed.
+
+## 🐳 Sandbox Image
+
+### Building
+
+The published base image (`ghcr.io/a2anet/adk-code-mode` on GitHub Container Registry) ships with `adk-code-mode-sandbox` already installed and works as-is for any tools whose execution is fully host-side. To bake in extra Python packages the model's code can `import`, extend it from your project's Dockerfile:
+
+```dockerfile
+FROM ghcr.io/a2anet/adk-code-mode:0.1.0
+RUN pip install --no-cache-dir pandas==2.2.*
+```
+
+```bash
+docker build -t myorg/code-mode:1.0 .
+```
+
+The same tag works for both local `DockerRuntime` and any future cloud runtime. Packages are baked in at build time — there is no runtime `pip install`. To build the local development image directly from this repo instead of the published one, run `make docker-image` (it builds the sandbox wheel and tags `adk-code-mode:local`).
+
+### Deploying with GCP
+
+`DockerRuntime` launches the sandbox via the Docker daemon on the agent host's machine, so the agent process must run somewhere it can reach a Docker socket. Supported targets today:
+
+- **Compute Engine VMs** with Docker installed.
+- **GKE pods** that mount the host's Docker socket (or run Docker-in-Docker).
+
+To deploy to a supported GCP environment, mirror the published image into your project's [Artifact Registry](https://cloud.google.com/artifact-registry) and point `DockerRuntime` at the registry tag:
+
+```bash
+# One-time per project / region.
+gcloud auth configure-docker <region>-docker.pkg.dev
+gcloud artifacts repositories create adk-code-mode \
+    --repository-format=docker \
+    --location=<region>
+
+# Pull, retag, push.
+docker pull ghcr.io/a2anet/adk-code-mode:0.1.0
+docker tag  ghcr.io/a2anet/adk-code-mode:0.1.0 \
+    <region>-docker.pkg.dev/<project>/adk-code-mode/adk-code-mode:0.1.0
+docker push <region>-docker.pkg.dev/<project>/adk-code-mode/adk-code-mode:0.1.0
+```
+
+Then in the agent:
+
+```python
+DockerRuntime(
+    image="<region>-docker.pkg.dev/<project>/adk-code-mode/adk-code-mode:0.1.0",
+)
+```
+
+If you extended the base image to install extra Python packages, push that derived image instead.
+
+## ⚙️ Configuration
+
+### Catalog overflow
+
+For very large tool surfaces the rendered catalog can dominate the prompt. `CodeModeCodeExecutor.max_catalog_chars` (default `50_000`) is a soft cap. When the catalog exceeds it, the callback drops every tool section and replaces it with a short prose note telling the model how to navigate `/tools/` from Python:
+
+```
+<tools>
+A `tools` package is available in the sandbox. List `/tools/` with
+`pathlib.Path('/tools').iterdir()`. Each entry is either a `.py` file
+(a top-level tool, importable as `from tools import <name>`) or a
+subdirectory (a namespace, with tools importable as
+`from tools.<namespace> import <name>`). To see a tool's signature and
+docstring, read its `.py` file with `open(...).read()`.
+</tools>
+```
+
+Tune `max_catalog_chars` for your model's context budget. Pass it on the executor:
+
+```python
+CodeModeCodeExecutor(tools=..., runtime=..., max_catalog_chars=20_000)
+```
+
+### Output truncation
+
+`max_output_chars=50_000` (default) caps the stdout and stderr handed back to the model. If either stream exceeds the cap, the model sees a head-and-tail view plus an inline marker:
+
+```
+Output exceeded 50,000 characters. Try again with a smaller output.
+Full stdout saved as artifact: code_mode/stdout/<execution-id>.txt
+```
+
+The full stream is saved as a regular session-scoped ADK artifact at the path printed in the marker. The model can recover it on demand the same way it loads anything else:
+
+```python
+from tools import load_artifact
+spilled = load_artifact(filename="code_mode/stdout/<execution-id>.txt")
+print(spilled["data"][-2000:])
+```
+
+So oversize output stays out of context but remains addressable. Developers can also fetch the same artifact directly via the configured `ArtifactService`.
+
+## 🏗️ Architecture
+
+ADK Code Mode has two pieces:
+
+**Host wheel (`adk-code-mode`).** Lives in the same Python process as your `LlmAgent`. Extends ADK's `BaseCodeExecutor`. The `before_model_callback` resolves your tools (including any `BaseToolset` instances), renders the catalog, and appends it to the system prompt. The catalog rendering and tool resolution are cached per-invocation so the follow-up `execute_code` call doesn't re-resolve toolsets. At code-execution time, the executor: (a) generates a small `tools/` Python package whose functions are thin stubs, (b) prepends the built-in `save_artifact` / `load_artifact` / `list_artifacts` tools (unless `include_artifact_tools=False`), (c) stages any `input_files` into `/workspace`, and (d) launches the sandbox.
+
+**Sandbox wheel (`adk-code-mode-sandbox`).** A stdlib-only package pre-installed in the container image. When the model's code calls a stub from `tools/…`, the stub sends a JSON-Lines frame over a TCP control connection to the host; the host runs the real tool (including ADK's `plugin_manager` / `before_tool` / `after_tool` callbacks) and sends the result back.
+
+The only things crossing the host ↔ sandbox boundary are: your code, tool call arguments, tool return values, and log frames. Wire format lives in `src/adk_code_mode/runtime/protocol.py` (and a byte-identical copy in the sandbox wheel so the two sides cannot drift).
+
+### What the model sees
+
+The system prompt the model receives is your `instruction` (which contains `CODE_MODE_SYSTEM_INSTRUCTION`) followed by a `<tools>` block appended by the callback:
+
+```
+…your instruction…
+
+<tools>
+
+# tools.slack
+
+from tools.slack import list_channels, send_message
+
+def list_channels() -> Any:
+    """List Slack channels."""
+    ...
+
+def send_message(*, channel: str, text: str, thread_ts: str | None = ...) -> Any:
+    """Send a message to a Slack channel.
+
+    Args:
+        channel: Channel ID like C123.
+        text: Message text.
+        thread_ts: Thread timestamp.
+    """
+    ...
+
+# tools
+
+from tools import save_artifact, load_artifact, list_artifacts
+
+def save_artifact(*, filename: str, content: str, mime_type: str | None = ...) -> int:
+    """Save an artifact to the session. Returns the new version number.
+    …
+    """
+    ...
+
+…
+
+</tools>
+```
+
+Each module is one section. The first line of each section is the exact import the model should copy. Bodies are `...` placeholders — the on-disk stubs do the real work via the control channel. When the rendered catalog grows past `max_catalog_chars`, the per-tool sections are dropped in favour of the prose note shown in [Catalog overflow](#catalog-overflow). At code-execution time, oversize stdout/stderr is replaced with a head-and-tail view plus a marker pointing at a session artifact (`code_mode/stdout/<execution-id>.txt`) the model can `load_artifact(...)` on demand.
+
+### Artifact wire format
+
+The artifact tools' wire format is JSON. Text and JSON-like MIME types travel as plain strings; binary content is base64-encoded by the model before `save_artifact` and decoded by the model after `load_artifact` (`load_artifact` returns `{"kind": "text" | "bytes", "data": str, "mime_type": str | None}`). All three call ADK's `ToolContext` artifact APIs on the host, so callbacks, plugins, and the configured artifact service run normally.
+
+## 🛡️ Safety
+
+- **Credentials never enter the sandbox.** API keys, OAuth tokens, DB connection strings — anything your tools use — stay in the host process. The container only gets the result of a tool call, not the means to make it. Tool dispatch goes through `src/adk_code_mode/tools/dispatcher.py`.
+- **Read-only rootfs by default.** `DockerRuntime(read_only=True)` is the default. The writable mount is `/workspace` for the current run; persistent data goes through host-side ADK artifact APIs.
+- **Bounded stdout/stderr.** `max_output_chars` caps what the model sees; overflow lands in an artifact for you, not in the model's context. Prevents runaway printing from poisoning the context or pushing large payloads into chat history.
+- **Bounded execution.** `timeout_seconds` caps overall runtime; `per_tool_timeout_seconds` caps each individual tool call.
+- **Resource limits.** `DockerRuntime` defaults to `mem_limit="1g"` and one full vCPU (`cpu_period=100_000`, `cpu_quota=100_000`). Override any of them on the runtime to raise or remove the cap.
+- **Network posture.** The container reaches the host over `host.docker.internal` for the control channel; outbound traffic otherwise follows Docker's default bridge. For stricter setups, pass a custom `network_mode` via `run_kwargs`.
+- **Control channel is token-gated.** Each `DockerRuntime.start()` mints a per-run shared secret and refuses any TCP peer that does not present it as the first line on connect. Defends against a process on the host racing the real sandbox onto the listener.
+- **Tool dispatch still runs ADK's guard callbacks.** `before_tool`, `after_tool`, `on_error`, and the plugin manager all fire for calls originating in sandbox code — any allow-list, redaction, or audit-log you already have keeps working.
+
+What this does **not** protect against: sandbox escapes in the container runtime itself, malicious tool implementations you wrote, exfiltration through legitimate tool calls (e.g. `send_email("attacker", ...)`), or side channels over the control pipe. Keep your tool surface least-privilege.
+
+## ⚠️ Limitations
+
+- **Credential-requesting tools are not supported in this release.** Tools or toolsets that need ADK to request credentials should not be exposed through Code Mode yet. Tool calls that request credentials, confirmations, UI widgets, agent transfer, escalation, compaction, agent state, rewind, or that yield without an immediate response (long-running tools) are rejected with a structured tool error — code mode has no resume path for an async function call.
+- **`DockerRuntime` deployment targets.** Does **not** work on Cloud Run, Cloud Functions, or Vertex AI Agent Engine — none of those expose a Docker daemon to the workload. Supported targets are Compute Engine VMs and GKE pods that can reach a Docker socket. A managed-sandbox runtime that targets the serverless environments is on the roadmap but not in this release.
+- **No state across executions.** Variables defined in one turn don't survive to the next; each `execute_code` call runs in a fresh sandbox. Use `save_artifact` / `load_artifact` to persist across turns, or `/workspace` within a single run.
+- **Sandbox is stdlib-only at runtime.** Extra Python packages must be baked into the image at build time; there is no runtime `pip install` from inside the sandbox.
+
+## 🛠️ Development
+
+```bash
+make install       # uv sync --group dev
+make ci            # ruff + mypy + pytest
+```
+
+Docker integration tests are opt-in:
+
+```bash
+uv run pytest -m docker
+```
+
+## 📄 License
+
+`adk-code-mode` is distributed under the terms of the [Apache-2.0](https://spdx.org/licenses/Apache-2.0.html) license.
+
+## 🤝 Join the A2A Net Community
+
+A2A Net is a site to find and share AI agents and open-source community. Join to share your A2A agents, ask questions, stay up-to-date with the latest A2A news, be the first to hear about open-source releases, tutorials, and more!
+
+- 🌍 Site: [A2A Net](https://a2anet.com)
+- 🤖 Discord: [Join the Discord](https://discord.gg/674NGXpAjU)

adk_code_mode-0.1.0.dist-info/RECORD

@@ -0,0 +1,23 @@
+adk_code_mode/__about__.py,sha256=0H6GNBbcL8zIcc4LIjpBwyFNtiAFeTkZ5LAqPOl2X4o,156
+adk_code_mode/__init__.py,sha256=vxb4whv2Wh_X-RHkwgR6G5EwW_Qy7A6ScWcHoekwtXQ,658
+adk_code_mode/_artifact_tools.py,sha256=vn-oGMbJfOMYNcS8VlCz0zhRYrf4SCf-hhYEL0LluxE,4739
+adk_code_mode/callback.py,sha256=u4-I04FFWs64NfUKLlal9VxO-mgNBovMg5EDf_C437E,2823
+adk_code_mode/executor.py,sha256=A1ks8g1usuG0xqy5Jc9GwM7qXPUa3oQWPKtwIf3uWPc,21894
+adk_code_mode/output.py,sha256=pxL3NEbqSx8cNJ_3jWzJI5p3Y6B7r4hLE39elW0PEtc,3249
+adk_code_mode/py.typed,sha256=AbpHGcgLb-kRsJGnwFEktk7uzpZOCcBY74-YBdrKVGs,1
+adk_code_mode/runtime/__init__.py,sha256=VXiP49KMxv5stYW0QH2EOrcCZ6QOuHyPBzZGMGQG9_8,344
+adk_code_mode/runtime/base.py,sha256=AGBouDeC9Y_aY6KJlslaOIzRFNKxXZcINDJWuHzdaCY,2520
+adk_code_mode/runtime/docker.py,sha256=K5L19TkvX7UMOjBeQct7RDWm_Fd3Mu2RA-q_T34hy9s,11814
+adk_code_mode/runtime/protocol.py,sha256=gybzBlaedv46mTMUF7s5Ux-Hsm4B_j42FnkOPJARLkk,5147
+adk_code_mode/tools/__init__.py,sha256=ZqMv0SXvfHqpO7CTqnKF0XxZFzTAavZcoLAGpg439ZU,173
+adk_code_mode/tools/catalog.py,sha256=in0bPqDOGFdN1TXSvQjbqr54Q12aLGbZNo2p1tGjhUQ,3462
+adk_code_mode/tools/dispatcher.py,sha256=8NDuGB1qL-YAq2s00yE-l_XumYlrTpP7K01ZlpMTR4U,11425
+adk_code_mode/tools/namespacing.py,sha256=Q83CIdEO7r6SluKEl1bxBPsM742SvBONOUIxBE__kw8,8112
+adk_code_mode/tools/normaliser.py,sha256=mT8OuAZUlPwm1WHCgSsIf9SFSATCdubuX48X3Nhgk64,2299
+adk_code_mode/tools/stubs.py,sha256=I5NsWctuRzlTGTZDXWnEKUOas-iI2b_F4Kmgx58fVGw,15942
+adk_code_mode/workspace/__init__.py,sha256=B0RmC5eHn-sujQIUXKg0JWeFaqkKFlfBDPfgFBOO8no,269
+adk_code_mode/workspace/files.py,sha256=FH3Y89ROkz2DteogVgt8kQkKmNFZNYccpMVPCPF_WcU,1268
+adk_code_mode-0.1.0.dist-info/METADATA,sha256=49l1xefru4KTlbgvvhMzPi1KW9QHV9YH-4sIbeaamGU,19810
+adk_code_mode-0.1.0.dist-info/WHEEL,sha256=QccIxa26bgl1E6uMy58deGWi-0aeIkkangHcxk2kWfw,87
+adk_code_mode-0.1.0.dist-info/licenses/LICENSE,sha256=xx0jnfkXJvxRnG63LTGOxlggYnIysveWIZ6H3PNdCrQ,11357
+adk_code_mode-0.1.0.dist-info/RECORD,,

adk_code_mode-0.1.0.dist-info/WHEEL

@@ -0,0 +1,4 @@
+Wheel-Version: 1.0
+Generator: hatchling 1.29.0
+Root-Is-Purelib: true
+Tag: py3-none-any

adk_code_mode-0.1.0.dist-info/licenses/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.