code-node-graph 0.1.0__tar.gz

code_node_graph-0.1.0/.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/Zensical 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

code_node_graph-0.1.0/CHANGELOG.md

@@ -0,0 +1,157 @@
+# Changelog
+
+Every change a user would notice, newest first ([Keep a Changelog](https://keepachangelog.com/en/1.1.0/)). Versions
+follow [Semantic Versioning](https://semver.org/); before 1.0, a minor version may change what a command does.
+## [Unreleased]
+
+## [0.1.0] - 2026-10-20
+
+### Added
+
+- A web platform for FastAPI, Flask and Django (`--platform web`, set on its own for an app it finds). What a
+  route is called with is the request, read like a Lambda handler's event: a FastAPI route's parameters (from the
+  path, the query, the body, `Query()`, `Header()`, `Annotated[...]`; not `Depends()`), a Flask view's URL values
+  and `flask.request` (`args`, `form`, `get_json()`), and a Django view's `request` (`GET`, `POST`, `body`) and URL
+  values. So SQL or a shell command built from a query string is flagged as injection, and the graph's first box is
+  "The request" with the fields the code reads (`path.order_id`, `query.q`, `json.team`).
+- Django's URL confs are entry points: a `urls.py` with `urlpatterns`, its `path()` and `re_path()` routes,
+  `include()` (routes come out under the path they're included at), class-based views (`View.as_view()`, a route
+  for each method) and Django REST framework routers (`router.register()`, a route for each ViewSet action). The
+  site's URL conf is offered before an app's it includes. `django.db.connection.cursor()` is read by the SQL plugin.
+- A web app's box in the graph shows its framework's logo (FastAPI, Flask or Django), on a white tile as other
+  logos are, and the docs' "What code-node knows" figure lists the three under "Runs on".
+- `examples/books-api`, a FastAPI app with a mistake for each thing the web platform finds, and a snapshot of
+  its page.
+- A call that blocks inside an `async def` route (requests, urllib, `time.sleep()`, boto3) is flagged: it holds up
+  every other request on the worker's event loop. A connection opened on every request is too.
+- Plugins that mix. Besides a platform (one per entry point), two new kinds of plugin stack: libraries, each turned
+  on when the code imports it, and deploy files, each read when it's in the folder. `code-node --plugins` lists
+  them, and other packages add their own through the `code_node.libraries` and `code_node.deploys` entry point
+  groups.
+- Library plugins for Redis, SQL (sqlite3, psycopg2, psycopg, PyMySQL, mysql-connector, asyncpg, SQLAlchemy),
+  MongoDB (PyMongo, Motor) and the OpenAI and Anthropic SDKs. The graph draws a box for each service they reach
+  (Redis, PostgreSQL, OpenAI) with what each call does (`SELECT products`, `SETEX receipt:{customer}`,
+  `chat.completions.create gpt-4o-mini`), and Step by step says it ("Reads from PostgreSQL (SELECT products)").
+- Deploy plugins for SAM / CloudFormation templates and `serverless.yml`. A function they name is an entry point,
+  whatever it's called, and the Lambda checks run against what the file says: environment variables that aren't
+  set, the Python it runs on, layers, its timeout, and AWS calls its role doesn't allow (marked "not allowed" in the
+  graph, with the SAM policy template that would allow them).
+- It follows text built from the input: SQL put together from the event is flagged "SQL injection" where it runs,
+  and so is a shell command (`shell=True`, `os.system`). A name set to such text says so in Step by step.
+- Findings across plugins: a client that has no timeout, worded for where it runs ("Lambda stops it at its 15 s
+  timeout"); a connection opened on every call of a Lambda handler; a call in a loop that a batch call would do
+  (`executemany()`, `mget()`, `insert_many()`, the Batch API); Redis `KEYS`.
+- Logos are sharp on an ordinary (1x) screen. They come in two sizes, as favicons do: AWS's detailed service
+  icons have a small mark too (the service's colour with a bold white symbol), which the page shows on a 1x screen,
+  and the full art on a 2x one. Badges are 32 px, AWS's icons fill theirs instead of sitting small on a white tile,
+  and other logos have less padding. The docs' figures, the home page graph and the screenshots pick the size they
+  draw at.
+- Real logos in the graph. AWS services (S3, DynamoDB, SNS, SQS, Lambda and about sixty more) and the services
+  libraries reach (Redis, PostgreSQL, MySQL, SQLite, MongoDB, OpenAI, Anthropic, Kafka...) show their own logo in
+  their box, in light and dark mode, where they had a line drawing; anything without one keeps it. The logos are
+  gilbarbara/logos (CC0), kept as .svg files in the package (`src/code_node/report/logos/`), and a page embeds
+  the ones it uses, so it still works offline. A library plugin can name one as
+  its icon (`icon = "kafka-icon"`).
+- Two new figures in the docs and the README, drawn with those logos: how the plugins mix on the cart example
+  (each finding marked with the plugins that found it together), and every service, platform and deploy file
+  code-node knows. Logos sit on a white tile in dark mode too, as they're drawn for one.
+- `examples/cart-service`, a Lambda function in a SAM template that uses PostgreSQL, Redis, OpenAI and boto3, and a
+  Plugins page in the docs drawn from it.
+- Line links to your editor: each step's card ("line 36 ↗") and each place in a box's code panel ("open ↗") opens
+  that line in VS Code, or in Cursor with `--editor cursor`. Inside WSL they open the Windows editor on the WSL
+  files. `--editor none` leaves them out, and the folder's full path with them.
+
+- The pages have a tab icon (code-node's logo), saved and served.
+
+- Click a box in the graph to read its code in a panel on the right: a function whole, with the lines that make
+  its calls lit, or a few lines around each place the code uses a service, a variable or its input. No JavaScript:
+  the panel opens with CSS (`:target`), and Back closes it. `GraphNode.code` lists the lines (`CodeSpan`), and
+  `page_blocks(..., sources=...)` takes the files to show them from.
+- Platforms: subclass `code_node.Platform` to say what another place code runs adds (its entry points, what
+  they're called with, its findings and wording), and add it with `register_platform` or a `code_node.platforms`
+  entry point in a package's `pyproject.toml`.
+- `code-node [folder]` reads a folder of Python code with `ast` (nothing is run) and opens a page showing how it works
+  from an entry point: a graph of what comes in, who calls whom and what each path reaches (AWS calls with their IAM
+  permissions, HTTP requests, environment variables), each call step by step, findings, and tables.
+- Entry points are found for you: `pyproject.toml` console scripts, Lambda handlers, FastAPI / Flask apps (each
+  route), Typer apps (each command), what runs under `if __name__ == "__main__":`, and functions named `main`.
+  When there are several, it asks which one.
+- Start from a file with `code-node path/to/main.py` or `code-node main.py:function` (or `Class.method`), from a
+  dotted name with `-e pkg.cli.main`, or search by part of a name with `-e save`.
+- `code-node --serve` puts the page on http://localhost:8765 and redraws it whenever a `.py` file changes. The
+  browser reloads at the same scroll position, and a page that can't be drawn says why until the next save.
+- `--all` draws every function however deep; `--depth` and `--functions` set the limits; `--mermaid` prints the
+  graph as Mermaid; `--list` lists the entry points.
+
+### Changed
+
+- A web app's own class (`FastAPI()`, `Flask()`, `APIRouter()`, `Blueprint()`) now comes from the web platform, so
+  an app found runs its checks. The summary no longer says "Each call runs app()" for an app object. Beside a step,
+  a field of the input is said in its platform's word (`event body.id` for Lambda, `request query.q` for a web
+  app), and the graph's input box is named for it when the kind of event can't be told ("The event", not "Its
+  input").
+- The graph has room to breathe and is drawn at its real size, no longer squeezed to the page's width. Gaps between
+  columns widen with the arrows through them, boxes are spaced further apart, columns are wider so names show whole
+  (a long method's name breaks after its class: `PluginManager.` / `_load_plugin()`), and the order with the fewest
+  crossing arrows is kept. Arrows that skip columns from one box (the environment's, start-up's) or into one run as
+  one line and part near the end, instead of each taking its own path, and the environment's and clients' arrows
+  are quieter until you point at a box. A column too tall to take in is split into lanes side by side, so a big
+  graph (`--functions 100`) is wide, not one long strip. Buttons over the graph zoom it (Auto, Fit, 100%, 150%)
+  and open it full screen, without JavaScript.
+- code-node now depends on PyYAML, to read deploy files.
+- `--serve` also redraws when a deploy file (`template.yaml`, `serverless.yml`) changes.
+
+- Step by step is easier to read. Each step in the list says what it does in plain words ("Takes `bucket` from the
+  event", "Reads from S3 (GetObject)", "Goes into `read_orders()`") instead of a cut-off line of code, with step
+  numbers in place of line numbers that jumped between files, and each function as a heading over its steps. A dot
+  marks the steps that reach AWS or the web. The card is roomier: that sentence as its headline, then where it is
+  and what it touches. Next is the one filled button, and Step over and Step out are now Skip call and Finish
+  `read_orders()`.
+- The graph picks its boxes by how much code each one leads to, not by how near it is: from the entry point it
+  keeps taking the function that leads to the most lines (and AWS calls, HTTP requests and environment variables)
+  below it. On code-node's own command it now draws `make_page`, `map_code`, `page_blocks` and `render_page`
+  instead of small helpers, and the graph is less than half as tall.
+- A box whose calls the graph leaves out says "+3 calls not drawn", and its code panel names them, instead of
+  looking like it does nothing.
+- It follows what Python calls for you: `super().__init__()` and other `super()` calls open the base class's method,
+  reading a `@property` (or `cached_property`) runs its getter, and a `with` block on one of your classes runs its
+  `__enter__` (what `as` names is what that returns) and, after the block, its `__exit__`.
+- Console scripts come from every `pyproject.toml` in the folder, not only the root's, so a monorepo's commands
+  (`libs/cli/pyproject.toml`) are found before its CI scripts.
+- SyntaxWarnings from the code being read (`"\d"` in a plain string) no longer show in the terminal.
+- It shows what it already knew about values. In Step by step, a line's card says what the names it sets now hold
+  (`store` holds an OrderStore, `self.table` a DynamoDB Table) and where its AWS call's arguments come from
+  (`Bucket ← env ARCHIVE_BUCKET`, `Key ← event Records[].s3.object.key`). A call's card says when it runs
+  ("only when `check(order)`"). The text and Mermaid output say the same, and the graph's AWS boxes list the sources
+  on hover.
+- A function called only under an `if` says so in its graph box ("when args.serve"), from the `if` nearest around
+  the call. Lines after `if not check(order): continue` (or `return`, `raise`, `break`) count as running only when
+  `check(order)`, rather than always.
+
+- The page is only two tabs now, Graph and Step by step. The title, the cards of numbers, the findings and the tables
+  under the graph (AWS calls and their IAM policy, environment variables, the event, functions, imports, HTTP
+  requests) are gone. The entry point and the folder sit at the right of the tab bar, which stays at the top as you
+  scroll. The graph still marks a warning on a box, such as an HTTP request with no timeout.
+- The graph and the steps are in tabs, Graph and Step by step, instead of one under the other.
+- Step by step is now a walk through the code in the order it runs, as a debugger steps: every step in a list, and
+  beside it the function the current step is in, its line lit, with a card saying what the line does and which calls
+  it's inside. Next goes into each function a line calls, Step over and Step out skip past them, and once a step is
+  clicked the arrow keys step through the rest. Click any numbered line in the code to jump to it. Still no
+  JavaScript, and a step is as quick on a page with thousands of them.
+- The paragraph summing up the code under the numbers is gone: the numbers, the findings and the graph say it.
+- Code on the page is set in Cascadia Mono when it's installed (the usual monospace font otherwise).
+- `code-node --serve` keeps the open tab and step when the page redraws.
+- The graph's code panel makes room beside the graph, rather than moving the whole page.
+
+- `code-node --serve` without `--port` takes the first free port from 8765, so you can serve several folders at
+  once instead of the second one failing. The served tab's title starts with the folder's name. `--port N` still
+  means exactly that port.
+
+- Lambda is now a platform plugin on top of a generic reader. Plain Python code no longer gets any Lambda check or
+  wording (a file written outside `/tmp` used to be marked amber in the graph), and Lambda handlers get the same
+  page as before.
+- `--platform NAME` runs a platform's checks whatever the entry point is; `--lambda` is short for
+  `--platform lambda`. `EntryPoint.is_lambda` and `PageOptions.is_lambda` are now `platform` (`"lambda"` or `""`).
+
+[Unreleased]: https://github.com/utkarsh5026/code-node/compare/v0.1.0...HEAD
+[0.1.0]: https://github.com/utkarsh5026/code-node/releases/tag/v0.1.0

code_node_graph-0.1.0/LICENSE

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