helius-python 0.0.1__tar.gz

helius_python-0.0.1/.editorconfig

@@ -0,0 +1,4 @@
+[*.py]
+indent_style = space
+indent_size = 4
+python_indent_open_paren = 4

helius_python-0.0.1/.github/workflows/python-publish.yml

@@ -0,0 +1,70 @@
+# This workflow will upload a Python Package to PyPI when a release is created
+# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python#publishing-to-package-registries
+
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
+
+name: Upload Python Package
+
+on:
+  release:
+    types: [published]
+
+permissions:
+  contents: read
+
+jobs:
+  release-build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.x"
+
+      - name: Build release distributions
+        run: |
+          # NOTE: put your own distribution build steps here.
+          python -m pip install build
+          python -m build
+
+      - name: Upload distributions
+        uses: actions/upload-artifact@v4
+        with:
+          name: release-dists
+          path: dist/
+
+  pypi-publish:
+    runs-on: ubuntu-latest
+    needs:
+      - release-build
+    permissions:
+      # IMPORTANT: this permission is mandatory for trusted publishing
+      id-token: write
+
+    # Dedicated environments with protections for publishing are strongly recommended.
+    # For more information, see: https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment#deployment-protection-rules
+    environment:
+      name: pypi
+      # OPTIONAL: uncomment and update to include your PyPI project URL in the deployment status:
+      # url: https://pypi.org/p/YOURPROJECT
+      #
+      # ALTERNATIVE: if your GitHub Release name is the PyPI project version string
+      # ALTERNATIVE: exactly, uncomment the following line instead:
+      # url: https://pypi.org/project/YOURPROJECT/${{ github.event.release.name }}
+
+    steps:
+      - name: Retrieve release distributions
+        uses: actions/download-artifact@v4
+        with:
+          name: release-dists
+          path: dist/
+
+      - name: Publish release distributions to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          packages-dir: dist/

helius_python-0.0.1/.gitignore

@@ -0,0 +1,220 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+*.lcov
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi/*
+!.pixi/config.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule*
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#   you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml

helius_python-0.0.1/AGENTS.md

@@ -0,0 +1,212 @@
+When implementing a function for a RPC method in the HeliusClient class, read the docs for the specific RPC method. For example, for the get_supply function (getSupply RPC method) you should read https://www.helius.dev/docs/rpc/guides/getsupply and https://www.helius.dev/docs/api-reference/rpc/http/getsupply.
+
+# API Reference
+
+The API reference is generated from **Google-style docstrings** on every public symbol in `src/helius/`. Whenever you add or modify a public method, model, or class, you MUST write or update its docstring following the rules below. The README's "Supported methods" table is a quick index only — the docstring is the source of truth.
+
+## Where docstrings live
+
+- **Client methods** (`HeliusClient.get_*`, `is_*`, `request_*`, etc.) — every public method gets a docstring. Private methods (`_send`, dunders) do not need one.
+- **Models** (`src/helius/models.py`) — every public model class gets a docstring describing what it represents. Individual fields don't need per-field docstrings if their names and types are self-explanatory; only document fields where the meaning, units, or nullability isn't obvious from the type alone.
+- **Builders / helpers** (`RpcRequest`) — class docstring describing purpose, plus one-line docstrings on each public method.
+
+## Client method docstring format
+
+Use Google-style sections. Order matters; omit any section that doesn't apply.
+
+```python
+def method_name(self, ...) -> ReturnType:
+    """One-line summary in the imperative mood, ending with a period.
+
+    Optional longer description: a paragraph or two on what the method does,
+    when to use it, and any non-obvious behavior. Keep this short — link to
+    the upstream Helius docs rather than restating them.
+
+    Args:
+        param_one: Description of the first parameter, including units
+            (lamports vs. SOL, slot vs. block height) when relevant. Mention
+            the upstream JSON field name only if it differs in a non-obvious
+            way from the snake_case Python name.
+        param_two: Description. Note constraints like "must be base-58
+            encoded" or "max 500_000 slots from `start_slot`".
+        commitment: Optional commitment level. Defaults to the node's default
+            when omitted.
+
+    Returns:
+        Describe the return shape. For tuples, describe each element in
+        order. For models, name the model and what it represents. For
+        primitives, name the unit (e.g. "Balance in lamports.").
+
+    Raises:
+        ValueError: When the arguments violate the documented constraints
+            (e.g. mutually exclusive params, mismatched pairs).
+
+    Note:
+        Only available on Devnet and Testnet, not Mainnet Beta.
+
+    See Also:
+        - Helius guide: https://www.helius.dev/docs/rpc/guides/<method>
+        - Helius API reference: https://www.helius.dev/docs/api-reference/rpc/http/<method>
+    """
+```
+
+Rules:
+
+- **Summary line** is one sentence, imperative mood, ≤ 88 chars, ends with a period. Example: `"Return the SOL balance of an account in lamports."`
+- **`Args:`** documents every parameter, even `commitment` and `min_context_slot`. One entry per param. Don't re-state the type — basedpyright already shows it.
+- **`Returns:`** is mandatory unless the method returns `None`.
+- **`Raises:`** is required if the method calls `raise` directly. Don't document exceptions that bubble up from `httpx` — those are covered by the library-wide error-handling docs.
+- **`Note:`** for network restrictions, version requirements, pagination limits, deprecation warnings, etc. One section per concern.
+- **`See Also:`** ALWAYS includes the Helius guide and API reference URLs for the underlying RPC method. This is the contract for an RPC wrapper — the docstring tells you what we do, the upstream docs tell you what the network does.
+- Keep prose tight. The docstring should be readable in `help(client.method)` without scrolling forever.
+
+## Model docstring format
+
+```python
+class Supply(BaseModel):
+    """Total, circulating, and non-circulating SOL supply, in lamports.
+
+    Returned as the `value` field of `getSupply`. All amounts are in
+    lamports (1 SOL = 1_000_000_000 lamports).
+
+    See Also:
+        - Helius API reference: https://www.helius.dev/docs/api-reference/rpc/http/getsupply
+    """
+    ...
+```
+
+Rules:
+
+- One-line summary + optional paragraph + `See Also:` linking the upstream docs that define the shape.
+- If a field has surprising semantics (e.g. `ui_amount` can be `None` when the mint has too many decimals, `non_circulating_accounts` is only populated when not excluded), document it inline with `Field(..., description="...")` or in the class docstring.
+
+## Conventions
+
+- Use **double-quoted triple strings** (`"""..."""`).
+- Wrap docstring lines at 88 columns.
+- Refer to parameters in backticks: `` `commitment` ``, `` `min_context_slot` ``.
+- Refer to other client methods with their snake_case name in backticks: `` `get_balance` ``.
+- Do NOT include the upstream JSON-RPC method name in the summary — that's already in the See Also URLs.
+- Do NOT copy-paste large chunks from the Helius docs. Summarize and link.
+- Examples (`Example:` section) are encouraged for methods with non-trivial argument combinations (e.g. `get_block_production`, `get_token_accounts_by_owner`), optional for everything else.
+
+## Implementation conventions
+
+- **If the RPC returns an `RpcResponse` wrapper (`{context, value}`), the Python method MUST return `(context, value)`** — never silently drop `context`. For methods whose `value` is itself a small composite, flatten the tuple (e.g. `get_latest_blockhash` returns `tuple[dict, str, int]`, not `tuple[dict, tuple[str, int]]`). Check the upstream Helius API reference page to see whether the response is wrapped.
+- Type-annotate the return shape exactly. `tuple[dict, X]`, not bare `tuple`, and not the unwrapped `X`. Mismatches between annotation and runtime shape break the docstring contract.
+- `value` can be `null` for some wrapped methods (e.g. `getAccountInfo` when the account doesn't exist, `getMultipleAccounts` entries for closed accounts). Reflect that in the return type with `| None` and handle it before calling `Model.model_validate(...)`.
+
+## Checklist for adding a new client method
+
+1. Read both Helius doc URLs for the RPC method (see the top of this file).
+2. Implement the method, following the **Implementation conventions** above — in particular, return `(context, value)` if the upstream response is wrapped.
+3. Add a docstring with `Args`, `Returns`, `Raises` (if any), `Note` (if any), and `See Also` with both Helius URLs.
+4. Add the method to the "Supported methods" table in `README.md`.
+5. Add tests per the Testing section.
+
+# Testing
+
+## Stack
+
+- `pytest` as the test runner.
+- `respx` for mocking the `httpx` transport. Do NOT use `unittest.mock` to patch `httpx` — always mock at the HTTP layer with `respx`.
+- No live network calls. Do NOT make real requests to `mainnet.helius-rpc.com`, `devnet.helius-rpc.com`, or any other Helius endpoint in tests. Devnet integration tests are explicitly out of scope for now.
+
+Add `pytest` and `respx` to a `[project.optional-dependencies] dev` table in `pyproject.toml` if not already present.
+
+## Layout
+
+```
+tests/
+  conftest.py            # shared fixtures (client factory, sample responses)
+  fixtures/              # captured JSON-RPC response bodies, one file per shape
+  unit/
+    test_rpc_request.py  # RpcRequest builder
+    test_models.py       # pydantic model validation against fixtures
+    test_client.py       # one test (or small group) per client method
+```
+
+## Three Layers
+
+### 1. `RpcRequest` builder — pure unit tests
+
+`RpcRequest` is pure logic with no I/O. Cover:
+
+- `add(value)` skips `None` unless `can_be_none=True`.
+- `set(key, value)` skips `None` unless `can_be_none=True`.
+- Positional params come before the config dict.
+- The config dict is appended as the last element of `params` only when it's non-empty.
+- `params` is omitted entirely from the payload when there are no positional or config values.
+- `method`, `id`, and `jsonrpc` are passed through correctly.
+
+These tests would have caught the current bug where `jsonrpc` is never added to the built payload. Fix bugs you find this way as separate commits, not as part of the test PR.
+
+### 2. Pydantic models — fixture-based unit tests
+
+For each model in `src/helius/models.py`:
+
+- Capture a real JSON-RPC `result` body once (manually, from the Helius docs' example responses or a one-off live call) and save it under `tests/fixtures/`.
+- Write a test that loads the fixture and calls `Model.model_validate(...)`. Assert a couple of representative fields parsed correctly (especially camelCase → snake_case via the alias generator).
+
+One fixture per model is enough. The goal is to catch schema mismatches (missing fields, wrong optionality, typos like `foudnation`), not to exhaustively assert every field.
+
+**Fixture keys must come from the Helius docs, not from the model.** If you write the fixture by reading the Python field names and camelCasing them, the test only proves the model agrees with itself — typos like `loaderScheduleSlotOffset` (should be `leaderScheduleSlotOffset`) will pass. Always copy the JSON keys verbatim from the upstream Helius example response.
+
+### 3. Client methods — `respx`-mocked tests
+
+For each method on `HeliusClient`, write at least one test that asserts **both** sides of the wire:
+
+- **Outgoing request:** the JSON body sent to Helius matches the JSON-RPC payload you expect — correct `method`, correct positional `params`, correct config object with snake → camel mapping, and optional arguments omitted when `None`.
+- **Return value:** the method correctly parses a canned response into the documented return shape (model, tuple, primitive, etc.).
+
+Also assert that the `api-key` query parameter is present on the request URL.
+
+**The mocked response body must mirror the real upstream shape.** Copy the `result` payload from the Helius docs' example response — do not invent a flatter shape by reading what the Python method indexes into. In particular, if the upstream method returns an `RpcResponse` wrapper (`{"context": {...}, "value": ...}`), the mock must include that wrapper, even if the client method only returns `value`. Otherwise a bug that reads `result["foo"]` instead of `result["value"]["foo"]` will pass the test and fail in production.
+
+Skeleton:
+
+```python
+import json
+import httpx
+import respx
+from helius import HeliusClient
+
+@respx.mock
+def test_get_balance():
+    route = respx.post("https://mainnet.helius-rpc.com/").mock(
+        return_value=httpx.Response(
+            200,
+            json={
+                "jsonrpc": "2.0",
+                "id": 1,
+                "result": {"context": {"slot": 1}, "value": 42},
+            },
+        )
+    )
+    with HeliusClient(api_key="test") as c:
+        assert c.get_balance("So11...112", commitment="finalized") == 42
+
+    sent = route.calls.last.request
+    assert sent.url.params["api-key"] == "test"
+    body = json.loads(sent.content)
+    assert body["method"] == "getBalance"
+    assert body["params"] == ["So11...112", {"commitment": "finalized"}]
+```
+
+For methods with branching logic (e.g. `get_block_production`, `get_token_accounts_by_owner`'s `mint` vs `program_id` validation, `get_account_info`'s `data_slice` pairing), add tests for each branch — including the `ValueError`s on invalid input combinations.
+
+## Conventions
+
+- Construct `HeliusClient` in tests with an explicit `api_key="test"` (or similar). Never rely on a real `.env` file.
+- Use the context-manager form (`with HeliusClient(...) as c:`) in tests so the `httpx.Client` is closed cleanly.
+- Group tests in `tests/unit/test_client.py` by method, but a single file is fine until it grows unwieldy.
+- Test names should describe the behavior, not the implementation: `test_get_balance_includes_commitment_in_config`, not `test_get_balance_calls_set`.
+- When adding a new client method, the PR must include: (a) a `respx` test asserting the request payload, and (b) a fixture-based model test if the method introduces or uses a model. This is enforced in `CONTRIBUTING.md`.
+
+## Running
+
+```bash
+pytest
+```
+
+All tests must pass and there must be no real network traffic. If a test fails because it tried to hit the network, that's a bug in the test — add the missing `@respx.mock` or `respx` route.

helius_python-0.0.1/CLAUDE.md

@@ -0,0 +1 @@
+@AGENTS.md

helius_python-0.0.1/CONTRIBUTING.md

@@ -0,0 +1,116 @@
+# Contributing
+
+Contributions to `helius-python` are very welcome! This project aims to be the
+**complete, typed Python client for [Helius](https://helius.dev)** and there
+is a lot of surface area still to cover. Every issue closed, RPC method added,
+typo fixed, and example improved moves the library closer to that goal.
+
+## Project Goals
+
+Before contributing, please read the [Goals section of the README](README.md#goals).
+Every change should serve at least one of:
+
+1. **Completeness** — 1:1 coverage of the entire Helius API surface.
+2. **Type safety** — fully typed parameters and responses.
+3. **Pythonic ergonomics** — `snake_case` names, context managers, sensible
+   defaults.
+4. **Zero magic** — thin, predictable wrappers that map directly to the
+   documented Helius API.
+
+If a change doesn't clearly support one of these goals, it probably isn't a
+good fit. When in doubt, open an issue first to discuss it.
+
+## Ways to Contribute
+
+There is no shortage of things to do. A few ideas, roughly ordered from
+easiest to most involved:
+
+- **Fix a bug.** Reproduce, write the fix, send the PR.
+- **Add a missing standard Solana JSON-RPC method.** Check the
+  [supported methods table in the README](README.md#supported-methods) — anything
+  in the [Solana JSON-RPC spec](https://solana.com/docs/rpc) that isn't listed
+  is fair game.
+- **Add a Helius-specific RPC extension** — enhanced transactions, DAS
+  (Digital Asset Standard) methods, priority fee estimation, etc.
+- **Add a Helius REST endpoint** — Enhanced Transactions API, Webhooks API,
+  Mint API, token metadata, address lookups, and more.
+- **Improve typing.** Tightening a `dict` return into a proper `pydantic`
+  model, narrowing a `str` into a `Literal`, or replacing `Any` with a real
+  type are all great contributions.
+- **Improve error handling.** A consistent exception hierarchy for transport
+  errors and Helius/Solana RPC errors is a known gap.
+- **Add streaming / websocket support** once the synchronous surface is
+  fleshed out.
+- **Improve docs and examples.** Clearer docstrings, better README snippets,
+  more realistic examples.
+
+If you're not sure where to start, browse the
+[open issues](https://github.com/markosnarinian/helius-python/issues).
+
+## Before You Start a Large Change
+
+**Please open an issue before working on anything non-trivial.** This includes:
+
+- Architectural changes or refactors that span multiple files.
+- New public APIs that aren't just wrapping an existing Helius/Solana endpoint.
+- Changes to the existing public method signatures or behavior.
+- Pulling in new runtime dependencies.
+- Anything you expect to take more than an afternoon.
+
+A quick conversation up-front saves everyone time and avoids the awkward case
+of a large PR that has to be redesigned or rejected. Small, focused PRs — one
+new RPC method, one bug fix, one model improvement — usually don't need
+prior discussion; just send them.
+
+## Codebase Conventions
+
+Please match the existing style of the codebase. Skim
+[`src/helius/client.py`](src/helius/client.py) and
+[`src/helius/models.py`](src/helius/models.py) before writing new code. In
+particular:
+
+- **Method names** are `snake_case` versions of the upstream RPC method
+  (`getAccountInfo` → `get_account_info`).
+- **Parameter names** are `snake_case` versions of the upstream JSON field
+  names (`minContextSlot` → `min_context_slot`).
+- **Use the `RpcRequest` builder** to construct request payloads — `add(...)`
+  for positional params, `set(key, value)` for fields inside the config
+  object. Don't build the JSON dict by hand.
+- **Type everything.** Parameters get explicit types, including `Literal`s
+  for fixed string options (`commitment`, `encoding`, etc.). Return types are
+  always declared.
+- **Model responses with `pydantic`.** Add a model in
+  [`src/helius/models.py`](src/helius/models.py) using the existing
+  `AliasGenerator(validation_alias=to_camel)` pattern instead of returning a
+  raw `dict`.
+- **Follow the docs.** When implementing a new RPC method, read both the
+  Helius guide and API reference for that method (see
+  [`AGENTS.md`](AGENTS.md)) and mirror the documented parameters and response
+  shape.
+- **Keep wrappers thin.** No surprise retries, caching, or transformations.
+  If the upstream API returns `{ context, value }`, return `(context, value)`
+  — don't flatten it.
+
+## Format and Lint Before Opening a PR
+
+Run the formatters and type checker before pushing. PRs that aren't formatted
+will be asked to reformat before review.
+
+```bash
+isort src
+black src
+basedpyright src
+```
+
+Make sure your change at least imports cleanly and the method you added
+actually works against a real Helius endpoint.
+
+## Pull Requests
+
+- Keep PRs focused. One method, one bug fix, or one refactor per PR.
+- Write a clear PR description: what changed, why, and a link to the relevant
+  Helius/Solana docs for any new endpoint.
+- Reference the issue your PR addresses (`Closes #123`).
+- Be patient — reviews happen as time allows.
+
+Thanks for contributing!

helius_python-0.0.1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Markos Narinian
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.