agent-signage 0.1.0__tar.gz

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

@@ -0,0 +1,33 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.9", "3.11", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install
+        run: pip install -e ".[dev]"
+
+      - name: Lint
+        run: ruff check src tests
+
+      - name: Test
+        run: pytest
+
+      - name: Selftest
+        run: agent-signage selftest

agent_signage-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,43 @@
+name: Publish to PyPI
+
+# Token-based, matching the rest of the Hermes Labs stack.
+#
+# The alternative -- PyPI trusted publishing via OIDC -- is more secure but
+# cannot be configured from a CLI: it is a web-only account setting with no
+# API, and twine has no account-management surface. Using the existing
+# user-scoped API token keeps releases scriptable and consistent with how
+# lintlang and the other packages in this org already ship.
+#
+# Requires one repository secret: PYPI_API_TOKEN.
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install build tools
+        run: pip install build twine
+
+      - name: Build sdist and wheel
+        run: python -m build
+
+      # PyPI runs this on upload anyway. Failing here gives a readable error
+      # instead of a rejected upload after the fact.
+      - name: Validate distributions
+        run: python -m twine check dist/*
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          password: ${{ secrets.PYPI_API_TOKEN }}

agent_signage-0.1.0/.gitignore

@@ -0,0 +1,11 @@
+__pycache__/
+*.py[cod]
+.pytest_cache/
+.ruff_cache/
+*.egg-info/
+dist/
+build/
+.coverage
+
+# Operator script: references internal push-gate env vars, stays local
+GO-LIVE.sh

agent_signage-0.1.0/CHANGELOG.md

@@ -0,0 +1,72 @@
+# Changelog
+
+All notable changes to this project are documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html)
+once it reaches 1.0. Before 1.0, minor version bumps may include breaking changes.
+
+## [0.1.0] - 2026-08-05
+
+### Added
+- Five signs, each selected against a documented failure report rather than invented:
+  `symlink_escape` (a path resolving through a symlink to outside the repository),
+  `conflict_markers` (unresolved merge markers still in the file),
+  `concurrent_worktree_edit` (another worktree has uncommitted changes to the same file),
+  `binary_edit` (NUL bytes present, so a text-shaped edit corrupts the file), and
+  `generated_file` (the header declares the file machine-generated).
+- `clear_caches()` on the git and content layers, called at the start of every evaluation, so
+  embedding the library in a long-lived process is as correct as the one-shot subprocess.
+- `docs/integrating.md` for harness maintainers: the stdin/stdout contract, the measured cost,
+  and the five things this will never do.
+
+### Changed
+- Signs whose only consequence is a bad write now fire on write-shaped tools only.
+- Git answers are memoised for the duration of one evaluation. An edit inside a repository went
+  from 119 ms to 71 ms; six signs were each re-spawning git to ask the same questions.
+- Ruff rules are now selected explicitly instead of inherited. The default set widens between
+  releases, so an unpinned dev dependency silently changed what CI enforced — a fresh clone
+  resolving a newer ruff would have failed CI on code that was clean when written.
+
+### Fixed
+- Deduplication is keyed per file, not per repository, so a second affected file in the same
+  session is still reported.
+
+## [0.0.8] - 2026-08-05
+
+### Added
+
+- First public release: a PreToolUse hook that reads a hook payload on stdin and,
+  when the target path is inside a git repository that is behind its configured
+  upstream, emits one line of `additionalContext` naming how many commits behind
+  and how old the upstream tip is. Silent otherwise.
+- One sign: `stale_checkout`. Registered via `agent_signage.signs.register`, which
+  third parties can call without forking.
+- CLI (`agent-signage`): `ack` to silence a sign until the observed state changes,
+  `clear` to remove stamps, `signs` to list the registry, `selftest` to assert the
+  runtime guarantees without a repository, `install` to add the hook entry to a
+  Claude Code `settings.json` idempotently, with a timestamped backup.
+- Suppression rules, all fact-based: vendored/build paths (`node_modules`, `vendor`,
+  `.venv`, `venv`, `site-packages`, `dist`, `build`, `.next`, `.tox`, `target`,
+  `__pycache__`, `.git`); detached HEAD; an in-progress bisect, rebase, merge, or
+  cherry-pick; a repo listed in `AGENT_SIGNAGE_IGNORE`; a repo already fetched
+  during the current session (via `AGENT_SIGNAGE_SESSION_START`); one sign per
+  (session, repo, sign); and state-keyed acknowledgement via `agent-signage ack`.
+- Freshness handling: remote knowledge older than `DEFAULT_FETCH_TTL_S` (30
+  minutes) triggers a detached background `git fetch` and stays silent for that
+  turn, with a cooldown (`FETCH_COOLDOWN_S`, 120s) so a slow fetch cannot spawn
+  one fetch per tool call. The hot path itself never touches the network.
+- Bounds: a 3-second whole-invocation deadline (`hook.DEADLINE_S`) and a 2-second
+  per-git-call timeout (`gitfacts.GIT_TIMEOUT_S`). The hook never emits a block
+  decision and always exits 0.
+- 40 tests over real synthetic git repositories in `tests/test_stale_checkout.py`.
+- Zero runtime dependencies. Python 3.9+.
+
+### Notes
+
+- Phase 0 risk retirement (`evals/baseline-0.0.7.json`): confirmed that
+  `PreToolUse` `additionalContext` reaches the model (verified end-to-end against
+  an isolated session that quoted the injected token back), and measured Python
+  startup on the hot path at 17ms against a planning assumption of ~100ms,
+  which is why this ships as a single Python implementation rather than the
+  originally planned two-language hot path.

agent_signage-0.1.0/CITATION.cff

@@ -0,0 +1,17 @@
+cff-version: 1.2.0
+message: If you use this software, please cite it as below.
+type: software
+title: agent-signage
+abstract: >-
+  Road signs for coding agents. A PreToolUse hook that checks, at the moment a
+  coding agent reads or edits a file, whether the file's git repository is
+  behind its upstream, and injects one true, checkable fact when it is.
+  Silent otherwise.
+authors:
+  - family-names: Bosch
+    given-names: Rolando
+    orcid: "https://orcid.org/0009-0005-4896-1112"
+version: 0.1.0
+date-released: '2026-08-05'
+license: Apache-2.0
+repository-code: "https://github.com/hermes-labs-ai/agent-signage"

agent_signage-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances
+  of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for
+moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail
+address, posting via an official social media account, or acting as an
+appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+roli@hermes-labs.ai. All complaints will be reviewed and investigated promptly
+and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

agent_signage-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,89 @@
+# Contributing
+
+## Setup
+
+```bash
+git clone https://github.com/hermes-labs-ai/agent-signage.git
+cd agent-signage
+python3 -m venv .venv && source .venv/bin/activate
+pip install -e ".[dev]"
+```
+
+## Running the checks
+
+```bash
+pytest                    # 68 tests, real synthetic git repos, no mocking of git
+ruff check src tests      # lint
+agent-signage selftest    # runtime guarantees, no repo needed
+```
+
+All three run in CI (`.github/workflows/ci.yml`) on Python 3.9, 3.11, and 3.13.
+A PR that doesn't pass all three won't be merged.
+
+## Project layout
+
+- `src/agent_signage/gitfacts.py` — every git call, isolated. Nothing here infers;
+  every function returns what git actually reported, or `None`.
+- `src/agent_signage/signs.py` — the sign registry and the one shipped sign,
+  `stale_checkout`.
+- `src/agent_signage/state.py` — session dedupe, acknowledgement, and fetch
+  cooldown stamps.
+- `src/agent_signage/hook.py` — the PreToolUse entry point: stdin JSON in,
+  `additionalContext` JSON or nothing out.
+- `src/agent_signage/__main__.py` — the CLI.
+- `tests/test_stale_checkout.py` — the behavioural spec. If you're unsure whether
+  a change is in scope, this file is the source of truth, not this document.
+
+## The bar for a new sign
+
+`src/agent_signage/signs.py` states it directly, and it's worth repeating here
+because it's the part contributors most often push against:
+
+> A sign must satisfy three properties, and anything that cannot is not a sign
+> and does not belong here:
+>
+> - **Sound** — it reports a measurement, never an inference. If it fires, the
+>   stated fact is true.
+> - **Silent** — it produces nothing at all when there is nothing to say. The
+>   cost of the mechanism in the common case is zero tokens.
+> - **Actionable** — it ends in the command that resolves it, so the reader is
+>   never left holding a problem with no next step.
+
+### Why a heuristic-based sign will be declined
+
+"Heuristic" here means anything that scores, estimates, guesses, or infers —
+confidence thresholds, "this file looks risky," "this diff smells large,"
+similarity scores, anything trained or tuned. That fails **sound** by
+construction: a heuristic can be wrong about the fact it's asserting, and a
+sign that can be wrong is not a road sign, it's an opinion wearing a road
+sign's format. The whole reason this project is worth putting in front of
+every file read is that when it speaks, the fact is true — every measurement
+in `gitfacts.py` is something git itself reported, and every suppression rule
+in `signs.py` is drawn from a fact (a marker file, a config value, a
+timestamp), never a guess.
+
+A heuristic sign also tends to fail **silent**: heuristics degrade gracefully
+by producing more noise at lower confidence, not less, which is the opposite
+of what this hook is for. And it tends to fail **actionable**, because a score
+or a hunch rarely has a single command that resolves it the way `git fetch`
+or `git rebase --continue` resolves a measured fact.
+
+If your proposed sign reports something git (or another tool) can state as a
+fact — "you are N commits behind," "this branch has no upstream," "this file
+is in `.gitignore` but tracked" — it's in scope. If it requires judgment about
+whether something is *probably* fine, it isn't, no matter how useful the
+judgment would be. Open an issue describing the fact you want to surface
+before writing code; it's a fast way to find out which side of that line it's
+on.
+
+### Style
+
+- No new runtime dependencies. Standard library only.
+- New git calls go in `gitfacts.py`, bounded by a timeout, returning `None` on
+  any failure. Never let a subprocess hang the hook.
+- New suppression logic must be a fact check, not a guess, per the section
+  above.
+- Tests build real temporary git repositories (see `tests/conftest.py` and the
+  fixtures in `tests/test_stale_checkout.py`), not mocked git output — the
+  soundness claim is "we report what git reports," and a mock only proves
+  fidelity to the mock's own assumptions.

agent_signage-0.1.0/LICENSE

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