mcpolish 0.1.0__tar.gz

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

@@ -0,0 +1,28 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python: ["3.11", "3.12"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python }}
+      - name: Install
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[dev]"
+      - name: Lint
+        run: ruff check src tests
+      - name: Test
+        run: pytest -q
+      - name: Self-lint
+        run: mcpolish lint examples/clean_server.py

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

@@ -0,0 +1,148 @@
+name: publish
+
+# Fires when you push a version tag like v0.1.0.
+# Build runs first without approval. Publish waits for the required reviewer
+# on the `pypi` environment.
+on:
+  push:
+    tags:
+      - 'v*'
+  workflow_dispatch:
+    inputs:
+      tag:
+        description: 'Tag to publish (e.g. v0.1.0). Used only for manual dispatch.'
+        required: false
+
+permissions: {}
+
+jobs:
+  # ----- 1. Build the wheel + sdist, verify metadata. No secrets needed. -----
+  build:
+    name: Build distribution
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+    outputs:
+      version: ${{ steps.version.outputs.version }}
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: '3.12'
+
+      - name: Install build tools
+        run: |
+          python -m pip install --upgrade pip
+          python -m pip install --upgrade build twine
+
+      - name: Confirm tag matches package version
+        id: version
+        run: |
+          set -e
+          TAG_NAME="${GITHUB_REF#refs/tags/}"
+          if [ -z "$TAG_NAME" ] || [ "$TAG_NAME" = "$GITHUB_REF" ]; then
+            TAG_NAME="${{ inputs.tag }}"
+          fi
+          TAG_VERSION="${TAG_NAME#v}"
+          PKG_VERSION=$(python -c "import tomllib,sys; print(tomllib.loads(open('pyproject.toml','rb').read().decode())['project']['version'])")
+          echo "tag=$TAG_NAME"
+          echo "tag_version=$TAG_VERSION"
+          echo "pyproject_version=$PKG_VERSION"
+          if [ "$TAG_VERSION" != "$PKG_VERSION" ]; then
+            echo "::error::tag $TAG_NAME ($TAG_VERSION) does not match pyproject version $PKG_VERSION"
+            exit 1
+          fi
+          echo "version=$PKG_VERSION" >> "$GITHUB_OUTPUT"
+
+      - name: Build sdist and wheel
+        run: python -m build
+
+      - name: Verify metadata with twine
+        run: twine check --strict dist/*
+
+      - name: Install built wheel and smoke-test the CLI
+        run: |
+          python -m venv /tmp/smoke
+          /tmp/smoke/bin/pip install --upgrade pip
+          /tmp/smoke/bin/pip install dist/*.whl
+          /tmp/smoke/bin/mcpolish --version
+          /tmp/smoke/bin/mcpolish doctor
+
+      - name: Show what will be uploaded
+        run: |
+          echo "==== Files to publish ===="
+          ls -la dist/
+          echo "==== Wheel contents ===="
+          unzip -l dist/*.whl | head -50
+
+      - name: Upload build artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+          retention-days: 7
+
+  # ----- 2. Publish to PyPI. Gated by the `pypi` environment's required reviewer. -----
+  publish:
+    name: Publish to PyPI
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/project/mcpolish/${{ needs.build.outputs.version }}/
+    permissions:
+      id-token: write  # required for PyPI Trusted Publishing (OIDC)
+    timeout-minutes: 15
+
+    steps:
+      - name: Download dist artifacts
+        uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: List artifacts under review
+        run: |
+          echo "Reviewer is approving publication of mcpolish ${{ needs.build.outputs.version }}"
+          ls -la dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          packages-dir: dist/
+          print-hash: true
+
+  # ----- 3. Verify the upload landed and is installable. -----
+  verify:
+    name: Verify install from PyPI
+    needs: [build, publish]
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Wait for PyPI index to settle
+        run: sleep 30
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: '3.12'
+
+      - name: Install from PyPI
+        run: |
+          python -m venv /tmp/verify
+          /tmp/verify/bin/pip install --upgrade pip
+          /tmp/verify/bin/pip install "mcpolish==${{ needs.build.outputs.version }}"
+          /tmp/verify/bin/mcpolish --version
+          /tmp/verify/bin/mcpolish doctor
+
+      - name: Summary
+        run: |
+          echo "## Published mcpolish ${{ needs.build.outputs.version }}" >> "$GITHUB_STEP_SUMMARY"
+          echo "" >> "$GITHUB_STEP_SUMMARY"
+          echo "Available at: https://pypi.org/project/mcpolish/${{ needs.build.outputs.version }}/" >> "$GITHUB_STEP_SUMMARY"
+          echo "" >> "$GITHUB_STEP_SUMMARY"
+          echo "Install with: \`pip install mcpolish==${{ needs.build.outputs.version }}\`" >> "$GITHUB_STEP_SUMMARY"

mcpolish-0.1.0/.gitignore

@@ -0,0 +1,69 @@
+# --- Python ---
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.Python
+*.egg-info/
+*.egg
+MANIFEST
+
+# --- Build artifacts ---
+build/
+dist/
+wheels/
+*.whl
+.eggs/
+pip-wheel-metadata/
+
+# --- Virtual environments ---
+.venv
+.venv-*
+venv/
+env/
+ENV/
+
+# --- Caches ---
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+.coverage.*
+coverage.xml
+htmlcov/
+.tox/
+.nox/
+.cache/
+
+# --- Editor / IDE ---
+.idea/
+.vscode/
+*.swp
+*.swo
+*~
+.project
+.pydevproject
+
+# --- OS ---
+.DS_Store
+.DS_Store?
+._*
+.Spotlight-V100
+.Trashes
+ehthumbs.db
+Thumbs.db
+desktop.ini
+
+# --- mcpolish runtime ---
+# LLM verdict cache (per-user, regenerated on demand)
+.mcpolish-cache.sqlite
+*.mcpolish.db
+# Reports written to disk during local runs
+*.sarif
+codequality.json
+mcpolish-report.json
+badge.svg
+mcpolish_badge.svg
+# Ad-hoc local scratch
+/tmp/
+scratch/

mcpolish-0.1.0/.pre-commit-hooks.yaml

@@ -0,0 +1,8 @@
+- id: mcpolish
+  name: mcpolish
+  description: Fast static linter for MCP servers
+  entry: mcpolish lint
+  language: python
+  types: [python]
+  pass_filenames: true
+  require_serial: true

mcpolish-0.1.0/.python-version

@@ -0,0 +1 @@
+3.11

mcpolish-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,75 @@
+# Contributor Code of Conduct
+
+## Our pledge
+
+We as members, contributors, and maintainers pledge to make participation in the mcpolish community a respectful and productive 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 behaviour that contributes to a positive environment:
+
+- Showing empathy and kindness toward other people.
+- Being respectful of differing opinions, viewpoints, and experiences.
+- Giving and gracefully accepting constructive feedback.
+- Accepting responsibility for our mistakes and learning from them.
+- Focusing on what is best for the project and the community.
+
+Examples of unacceptable behaviour:
+
+- Sexualised language or imagery, or unwelcome attention of any kind.
+- Trolling, insulting or derogatory comments, and personal or political attacks.
+- Public or private harassment.
+- Publishing other people's private information without explicit permission.
+- Conduct which could reasonably be considered inappropriate in a professional setting.
+
+## Enforcement responsibilities
+
+Project maintainers are responsible for clarifying and enforcing these standards. Maintainers have the right to remove, edit, or reject comments, commits, code, issues, pull requests, and other contributions that are not aligned with this Code of Conduct, and will communicate the reasons when doing so.
+
+## Scope
+
+This Code of Conduct applies in all project spaces (issues, pull requests, discussions, chat channels) and when an individual is officially representing the project in public spaces. Examples of representing the project include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Reporting
+
+If you experience or witness behaviour that violates this Code of Conduct, please report it by emailing the maintainers at conduct@mcpolish.dev. All reports will be reviewed and investigated promptly and fairly.
+
+The maintainers will respect the privacy and security of the reporter of any incident.
+
+## Enforcement guidelines
+
+Maintainers will follow these guidelines when determining the consequences for any action they deem to be in violation of this Code of Conduct.
+
+### 1. Correction
+
+**Impact**: Use of inappropriate language or other behaviour deemed unprofessional or unwelcome.
+
+**Consequence**: A private, written warning from the maintainers, explaining the nature of the violation and why the behaviour was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behaviour. 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 project spaces and on external channels. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary ban
+
+**Impact**: A serious violation of community standards, including sustained inappropriate behaviour.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the project for a specified period of time. No public or private interaction with the people involved is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent ban
+
+**Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behaviour, 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 project.
+
+## Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
+
+Community Impact Guidelines are inspired by Mozilla's code of conduct enforcement ladder.
+
+For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq.

mcpolish-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,133 @@
+# Contributing to mcpolish
+
+Thank you for taking the time to contribute. This page explains how to get a development environment set up, the conventions the project follows, and how to propose changes.
+
+## Ways to contribute
+
+| If you have... | Open a |
+|---|---|
+| Found a bug | [Bug report issue](https://github.com/vtensor/mcpolish/issues/new?labels=bug) |
+| Want a new rule | [Rule proposal issue](https://github.com/vtensor/mcpolish/issues/new?labels=rule-proposal) with a citation or operational evidence |
+| Spotted a doc problem | Pull request that edits the file under `docs/` |
+| Fixed a bug | Pull request linked to the issue |
+| Want to discuss design | [Discussion](https://github.com/vtensor/mcpolish/discussions) |
+
+Before opening a large pull request, please open an issue first so we can agree on the approach. Small fixes (typos, single-rule patches, doc edits) do not need an issue first.
+
+## Development setup
+
+mcpolish needs Python 3.11 or newer.
+
+```bash
+git clone https://github.com/vtensor/mcpolish.git
+cd mcpolish
+python -m venv .venv
+source .venv/bin/activate
+pip install -e ".[dev,llm]"
+```
+
+The `dev` extra adds pytest, mypy, and ruff. The `llm` extra adds the OpenAI and Anthropic SDKs needed for the three LLM-judged rules.
+
+## Running the tests
+
+```bash
+pytest -q
+```
+
+The suite has 132 tests and runs in under one second. It must stay green for any pull request to be merged.
+
+Useful subsets:
+
+```bash
+pytest -k MP010                 # tests for one rule
+pytest tests/unit/test_scenarios.py -v
+pytest --tb=short               # shorter failure traces
+```
+
+## Linting and type-checking
+
+```bash
+ruff check src tests
+mypy src/mcpolish
+mcpolish lint examples/clean_server.py
+```
+
+All three must pass before merge.
+
+## Running mcpolish on itself
+
+mcpolish lints MCP servers; the examples under `examples/` are real MCP servers. Use them as a smoke test:
+
+```bash
+mcpolish lint examples/clean_server.py       # must score 100
+mcpolish lint examples/smelly_server.py --fail-on never
+```
+
+## Adding a new rule
+
+This is the most common kind of contribution. The shape:
+
+1. **Open a rule proposal issue.** Cite the paper, blog post, or operational evidence that supports the rule.
+2. **Pick the next stable ID** in the appropriate category:
+   - Schema: MP001-MP009
+   - Naming: MP010-MP019
+   - Description: MP020-MP029
+   - Consistency: MP030-MP039
+   - Security: MP040-MP049
+3. **Add the rule file** under `src/mcpolish/rules/<category>/MPxxx_name.py`. Follow the shape of existing rules.
+4. **Register it** with the `@register` decorator so the rule shows up at import time.
+5. **Add a fixture** under `tests/fixtures/scenarios/rule_MPxxx.py` that triggers exactly your rule.
+6. **Add tests** under `tests/unit/test_rules_<category>.py` plus the parametrised entry in `tests/unit/test_scenarios.py`.
+7. **Write the docs** under `docs/rules/MPxxx.md`. Follow the template in [docs/rules/MP010.md](docs/rules/MP010.md).
+8. **Update the indexes**: `docs/rules/index.md`, `docs/concepts/what-mcpolish-checks.md`, and `docs/methodology.md`.
+
+Once shipped, a rule ID is stable forever. The default severity may change between releases. The ID and the human name never do.
+
+## Style
+
+- Plain English in docs and comments. Avoid em dashes and box-drawing characters; the project deliberately uses ASCII only.
+- Sentences under 25 words where reasonable.
+- Define every short form on first use, or link to the [glossary](docs/concepts/glossary.md).
+- Code style follows `ruff` defaults. Run `ruff format` before committing.
+- Type hints everywhere. `mypy` runs in strict mode for new code paths.
+
+## Pull request checklist
+
+Before opening a pull request:
+
+- [ ] Tests pass: `pytest -q`
+- [ ] Lint passes: `ruff check src tests`
+- [ ] No forbidden characters: `grep -rPn "[\x{2014}\x{2013}\x{2500}-\x{257F}]" src tests docs README.md` returns nothing (Unicode em dash U+2014, en dash U+2013, and box-drawing block)
+- [ ] Internal markdown links resolve (run the link-check script in `tests/` if present, or open the changed pages)
+- [ ] New code paths covered by tests
+- [ ] Docs updated where behaviour changed
+- [ ] `VERIFICATION.md` updated if a verification scenario changed
+
+## Commit messages
+
+Use a short imperative subject line:
+
+```
+add MP015 require-tool-version
+fix MP004 firing on auto-derived schemas
+docs: expand MP010 examples
+```
+
+Long-form commit bodies are welcome for non-trivial changes.
+
+## Release process (maintainers)
+
+1. Bump `__version__` in `src/mcpolish/_version.py`.
+2. Bump `version` in `pyproject.toml`.
+3. Update `CHANGELOG.md`.
+4. Tag the release: `git tag -a v0.x.y -m "v0.x.y"`.
+5. Push: `git push --tags`.
+6. CI publishes the wheel to PyPI.
+
+## Code of Conduct
+
+This project follows the [Contributor Covenant](CODE_OF_CONDUCT.md). Participation in this project means agreeing to abide by it.
+
+## License
+
+By contributing, you agree that your contributions will be licensed under the project's Apache 2.0 [LICENSE](LICENSE).

mcpolish-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 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 accept 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 the sole responsibility 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 2026 Vikram Dev
+
+   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.