@minionry/minion 0.7.36

package/LICENSE

@@ -0,0 +1,14 @@
+Minionry Commercial License
+
+Copyright (c) 2025-present Minionry, Inc. All rights reserved.
+
+This software is not open-source. It is provided under a commercial
+license, and your rights to install, use, and (where the Minionry Terms
+of Service expressly permit it) distribute this software are set out
+there, together with all applicable restrictions, termination, and
+disclaimer terms:
+
+https://app.minionry.com/terms
+
+If you do not agree to the Minionry Terms of Service, you may not
+install or use this software.

package/PRIVACY.md

@@ -0,0 +1,357 @@
+# Minionry Privacy Policy
+
+**Effective Date:** March 2026
+**Last Updated:** September 2026
+
+---
+
+## 1. Introduction
+
+Minionry, Inc. ("we", "us", "our", "Minionry") is committed to protecting your privacy and handling your personal data with transparency and care. This Privacy Policy explains how we collect, use, store, share, and protect your information when you use the Minionry platform, including the Minionry CLI, the web application at app.minionry.com, and all related services (collectively, the "Service").
+
+We are the **data controller** for personal data processed through the Service. Our registered place of business is in the United States.
+
+**Privacy contact:** onit@minionry.com
+**Website:** https://minionry.com
+
+If you have questions about how we handle your data, please contact us before using the Service.
+
+---
+
+## 2. Scope and Applicability
+
+This policy applies to:
+
+- Users who access minionry.com from any jurisdiction, including the European Union, United Kingdom, and European Economic Area (EEA)
+- Users who install and run the Minionry CLI on their local machines
+- Visitors to our website
+
+This policy does not apply to third-party services, websites, or tools that you may access through or alongside Minionry.
+
+---
+
+## 3. Data We Collect and Lawful Basis
+
+We only process personal data where we have a valid lawful basis under Article 6 of the GDPR (or equivalent applicable law). The lawful basis for each category of processing is identified below.
+
+### 3.1 Account Information
+
+**What we collect:**
+- Email address
+- Name (optional, if provided during registration)
+- Account identifier and hashed password
+- Device identifiers and hashed device tokens (for the device code authentication flow)
+
+**Lawful basis:** Performance of a contract (Article 6(1)(b) GDPR) -- this data is necessary to create and maintain your account and provide the Service.
+
+**Storage:** Neon Postgres (serverless managed database).
+
+### 3.2 Session and Workspace Data
+
+**What we collect:**
+- Workspace connection settings
+- Session metadata (connection timestamps, session identifiers, tab state)
+- WebSocket connection state (held temporarily in Redis for active sessions)
+
+**What we do NOT store:** File contents and source code transmitted through the WebSocket relay pass through our platform servers in transit but are **not stored** on our servers. They exist only in your active session.
+
+**Lawful basis:** Performance of a contract (Article 6(1)(b) GDPR) -- session data is necessary to provide real-time workspace relay functionality.
+
+**Storage:** Neon Postgres (persistent session metadata), Redis (ephemeral active-session state, not persisted beyond the session lifecycle).
+
+### 3.3 Telemetry Data
+
+By default, the Minionry CLI sends telemetry to improve the software. Usage analytics are keyed to a random identifier generated on your machine, not to your account. We process two categories of telemetry:
+
+**Error Reporting (via Sentry):**
+- Stack traces and error messages
+- Minionry version and environment
+- Operating system and architecture
+- Node.js version
+
+**Usage Analytics (via PostHog):**
+- Feature usage patterns
+- Session duration
+- Command frequency
+- Events such as the CLI starting and stopping, agent and terminal sessions, and safety-check outcomes, with timing and counts
+- The name (not the path or contents) of the folder the CLI was started in
+- Operating system, architecture, Node.js version, and Minionry version
+
+**What we DO NOT collect:**
+- File contents or source code
+- API keys or credentials
+- Personal identifying information in error reports
+- IP addresses (stripped before storage)
+
+**Lawful basis:** Legitimate interests (Article 6(1)(f) GDPR) -- we have a legitimate interest in understanding how the software is used and identifying bugs in order to improve reliability and performance. This interest is not overridden by your rights because telemetry is pseudonymised (keyed to a random device identifier), you retain the ability to opt out at any time, and we collect the minimum data necessary.
+
+**How to opt out:**
+
+```bash
+export MINIONRY_TELEMETRY=0
+```
+
+or set `"telemetry": false` in `~/.minionry/config/telemetry.json`.
+
+When telemetry is disabled:
+- No error reports are sent to Sentry
+- No usage analytics are sent to PostHog
+- Core functionality remains unchanged
+
+### 3.4 Local Audit Logs
+
+The Minionry CLI keeps a local audit log of the actions it reviews on your machine, at:
+
+```
+<workingDir>/.minionry/logs/bouncer-audit.jsonl
+```
+
+**Important:** These audit logs are stored **only on your local machine**. They are never transmitted to Minionry servers. However, because they may record the content of tool calls (for example, file paths, command arguments, or code snippets), they may incidentally contain personal data.
+
+You are responsible for the security and retention of these local files. You may delete them at any time. We recommend reviewing this log periodically if you operate in a sensitive environment.
+
+**Lawful basis:** Not applicable for platform purposes -- this data is not processed by Minionry, Inc. It is retained locally on your device and is outside our control.
+
+### 3.5 Credentials
+
+Authentication credentials (including device tokens and session keys) are stored locally on your machine at `~/.minionry/credentials/platform.json` with restrictive file permissions (chmod 600). These credentials are not transmitted to or stored on Minionry's platform servers beyond what is necessary for active authentication verification.
+
+**Lawful basis:** Performance of a contract (Article 6(1)(b) GDPR) -- credentials are necessary to authenticate your access to the Service.
+
+### 3.6 Payment and Financial Data
+
+If you purchase paid features of the Service, we will collect and process payment information, including:
+
+- Billing contact information (name, email, billing address)
+- Payment method details (processed by Stripe; we do not store raw card numbers)
+- Transaction history and subscription status
+
+**Lawful basis:** Performance of a contract (Article 6(1)(b) GDPR) for billing and subscription management; Legal obligation (Article 6(1)(c) GDPR) for financial record-keeping and tax compliance.
+
+**Note:** Payment processing will be handled by a third-party processor (Stripe). Its privacy policy governs the data it collects independently.
+
+### 3.7 AI Agents and Model Providers
+
+The Minionry CLI runs AI agent tools that you install and sign in to yourself (for example, Claude Code). When you run an agent, your prompts and the files, command output, and other content the agent reads are sent to that agent's provider under your own account or API key with that provider, and are governed by your agreement with them. The CLI also uses an AI model, through the same agent tools, to review some agent actions before they run and to assist features such as commit messages; the content under review is sent to that provider in the same way.
+
+Some Minionry apps request AI completions through our servers. Those requests are sent to our model provider (see Section 6). We record usage (model and token counts) for each request, not its content.
+
+**Lawful basis:** Performance of a contract (Article 6(1)(b) GDPR) -- this processing is necessary to provide the features you request.
+
+---
+
+## 4. Cookies and Tracking Technologies
+
+When you use minionry.com, we and our third-party service providers use cookies and similar tracking technologies.
+
+### 4.1 Types of Cookies We Use
+
+| Category | Purpose | Examples | Can be disabled? |
+|---|---|---|---|
+| Strictly necessary | Authentication, session management, security | Session cookies | No -- required for the Service |
+| Analytics | Understanding how users interact with the platform | PostHog analytics cookies | Yes -- via telemetry opt-out or browser settings |
+| Error tracking | Capturing errors for debugging | Sentry session replay (if enabled) | Yes -- via telemetry opt-out |
+
+### 4.2 Managing Cookies
+
+You can control cookies through:
+
+- **Browser settings:** Most browsers allow you to block or delete cookies. Blocking strictly necessary cookies will prevent the Service from functioning.
+- **Telemetry opt-out:** Setting `MINIONRY_TELEMETRY=0` (or `"telemetry": false` in `~/.minionry/config/telemetry.json`) disables analytics and error tracking.
+- **Do Not Track:** We respect browser-level Do Not Track signals for analytics processing.
+
+We do not use cookies for advertising or cross-site tracking.
+
+---
+
+## 5. How We Use Your Information
+
+We use personal data only for the purposes for which it was collected or for compatible purposes. Specifically:
+
+- Provide, operate, and maintain the Minionry Service
+- Authenticate your identity and manage your devices
+- Process payments and manage subscriptions
+- Identify and fix bugs and crashes
+- Improve software performance and features
+- Communicate service updates, security notices, and changes to this policy
+- Ensure security, detect abuse, and protect against fraud
+- Comply with applicable legal obligations
+
+We do not use your personal data for automated decision-making or profiling that produces legal or similarly significant effects.
+
+---
+
+## 6. Data Sharing and Processors
+
+We do not sell your personal information. We do not share personal data with third parties for their own marketing purposes.
+
+We engage the following data processors, each bound by data processing agreements and appropriate contractual safeguards:
+
+| Processor | Role | Data Processed | Location |
+|---|---|---|---|
+| **Neon** | Managed Postgres database | Account data, session metadata, device records | United States |
+| **Hetzner Online GmbH** | Relay server hosting (VPS) | Server-side data in transit (the relay does not persist your code) | Germany (EU) |
+| **Cloudflare** | DNS, TLS, and edge proxy for app.minionry.com | Request metadata (IP, headers) in transit | Global edge network |
+| **Vercel** | Web frontend hosting (minionry.com) | Web request logs, static asset delivery | United States / Global CDN |
+| **Sentry** | Error tracking and monitoring | Error reports, stack traces | United States |
+| **PostHog** | Product analytics | Pseudonymous usage events | United States (EU hosting option available) |
+| **Anthropic** | AI model provider for completions requested by Minionry apps | Request content, in transit | United States |
+| **Stripe** | Payment processing (once paid features are offered) | Billing information, payment method data | United States |
+
+We may also disclose personal data in the following circumstances:
+
+- **Legal requirements:** Where required by applicable law, court order, or regulatory authority, including to comply with valid legal process.
+- **Protection of rights:** Where necessary to protect the rights, property, or safety of Minionry, our users, or the public.
+- **Business transfers:** In connection with a merger, acquisition, or sale of all or a portion of our assets, in which case we will provide notice before personal data is transferred and becomes subject to a different privacy policy.
+
+---
+
+## 7. International Data Transfers
+
+Minionry, Inc. is based in the United States. If you are located in the European Union, United Kingdom, EEA, or other jurisdictions with data transfer restrictions, your personal data is transferred to and processed in the United States.
+
+We ensure that such transfers are subject to appropriate safeguards as required by applicable law. Specifically:
+
+- **Standard Contractual Clauses (SCCs):** We rely on the European Commission-approved Standard Contractual Clauses (including, where applicable, the UK International Data Transfer Addendum) as the transfer mechanism for personal data transferred from the EU/EEA/UK to the United States.
+- **Processor agreements:** All third-party processors who receive personal data from EU/EEA/UK users are required to maintain SCCs or another valid transfer mechanism.
+
+You may request a copy of the applicable transfer safeguards by contacting us at onit@minionry.com.
+
+---
+
+## 8. Data Retention
+
+We retain personal data only for as long as necessary for the purposes for which it was collected, or as required by law.
+
+| Data Category | Retention Period |
+|---|---|
+| Account data (email, name, account ID) | Retained while your account is active; deleted within 30 days of account deletion |
+| Device records and hashed tokens | Deleted upon device deregistration or account deletion |
+| Session metadata | Retained for up to 12 months from the session date |
+| Redis session state | Ephemeral; purged at session end |
+| Telemetry -- error reports (Sentry) | Up to 30 days |
+| Telemetry -- usage analytics (PostHog) | Up to 90 days |
+| Payment records | Retained for up to 7 years as required by applicable tax and financial regulations |
+| Local audit logs (`bouncer-audit.jsonl`) | Stored only on your machine; not subject to our retention schedule |
+
+When your account is deleted, we will delete or anonymise your personal data within 30 days, unless a longer retention period is required by law or legitimate business necessity (for example, for fraud investigation or to resolve outstanding disputes).
+
+---
+
+## 9. Your Rights Under GDPR and Applicable Law
+
+If you are located in the European Union, United Kingdom, or EEA, you have the following rights with respect to your personal data:
+
+| Right | Description |
+|---|---|
+| **Right of access** | Request a copy of the personal data we hold about you |
+| **Right to rectification** | Request correction of inaccurate or incomplete personal data |
+| **Right to erasure** | Request deletion of your personal data ("right to be forgotten"), subject to legal retention obligations |
+| **Right to restriction** | Request that we restrict processing of your personal data in certain circumstances |
+| **Right to data portability** | Receive your personal data in a structured, commonly used, machine-readable format |
+| **Right to object** | Object to processing based on legitimate interests; object to direct marketing at any time |
+| **Right to withdraw consent** | Where processing is based on consent, withdraw it at any time without affecting prior processing |
+| **Right not to be subject to automated decisions** | Not be subject to solely automated decisions that produce legal or similarly significant effects |
+
+**Response timeframe:** We will respond to all valid data subject requests within **30 days** of receipt. Where requests are complex or numerous, we may extend this period by a further two months, in which case we will notify you within the initial 30-day period.
+
+**How to exercise your rights:** Submit a request by email to onit@minionry.com. We may need to verify your identity before processing your request.
+
+**Residents of other jurisdictions:** If you are a California resident, you may have additional rights under the CCPA/CPRA, including the right to know, delete, correct, and opt out of sale (we do not sell data). Contact us at onit@minionry.com for jurisdiction-specific requests.
+
+---
+
+## 10. Right to Lodge a Complaint
+
+If you believe we have not handled your personal data in accordance with applicable law, you have the right to lodge a complaint with a supervisory authority.
+
+- **EU:** Contact the data protection authority in your EU member state. A list of EU supervisory authorities is available at: https://edpb.europa.eu/about-edpb/about-edpb/members_en
+- **UK:** Contact the Information Commissioner's Office (ICO) at https://ico.org.uk
+
+We ask that you contact us first at onit@minionry.com so that we have the opportunity to address your concern before you escalate to a supervisory authority.
+
+---
+
+## 11. Data Protection Officer
+
+At Minionry's current scale and given the nature of our processing activities, we are not required to appoint a Data Protection Officer (DPO) under Article 37 of the GDPR. We nonetheless take privacy obligations seriously and have designated a privacy contact to handle data protection matters.
+
+**Privacy contact:** onit@minionry.com
+
+If our processing activities change in a way that triggers the DPO requirement, we will appoint a DPO and update this policy accordingly.
+
+---
+
+## 12. Data Security
+
+We implement appropriate technical and organisational measures to protect your personal data against unauthorised access, accidental loss, destruction, or disclosure:
+
+- Encryption in transit using TLS/HTTPS for all platform communications
+- Secure local credential storage with restrictive file permissions (chmod 600)
+- Hashed device tokens (SHA-256) -- plaintext tokens are never stored
+- Neon Postgres encryption at rest
+- Regular security reviews of platform infrastructure
+- Minimal data collection -- we do not collect what we do not need
+- Access controls limiting personnel access to personal data on a need-to-know basis
+
+No method of electronic transmission or storage is 100% secure. We cannot guarantee absolute security, but we are committed to maintaining industry-standard protections.
+
+---
+
+## 13. Data Breach Notification
+
+In the event of a personal data breach that is likely to result in a risk to the rights and freedoms of individuals, we will:
+
+- Notify the relevant supervisory authority **within 72 hours** of becoming aware of the breach, as required by Article 33 of the GDPR
+- Notify affected individuals **without undue delay** where the breach is likely to result in a high risk to their rights and freedoms, as required by Article 34 of the GDPR
+- Document all data breaches in our internal breach register, regardless of whether notification is required
+
+Breach notifications to affected users will be sent to the email address associated with your account. We recommend keeping your account email address current.
+
+---
+
+## 14. Children's Privacy
+
+**General use:** The Service is not directed to children under the age of **13**. We do not knowingly collect personal data from children under 13. If you believe a child under 13 has provided us with personal data, please contact us at onit@minionry.com and we will promptly delete that information.
+
+**Payment features:** Access to paid features and any functionality involving financial transactions requires users to be at least **18 years of age** (or the age of majority in their jurisdiction, if higher). We do not knowingly permit minors to engage in payment-related activities on the platform.
+
+If you are a parent or guardian and believe your child has used or registered for the Service in violation of this policy, please contact us.
+
+---
+
+## 15. Software License
+
+Your use of the Minionry CLI and the `@minionry/*` packages is governed by the license terms included with each package. This Privacy Policy applies to your use of the hosted Service (the minionry.com platform and relay server) and to any personal data processed in connection with your Minionry account, regardless of which client you use.
+
+---
+
+## 16. Changes to This Policy
+
+We may update this Privacy Policy from time to time to reflect changes in our practices, technology, legal requirements, or other factors.
+
+When we make material changes, we will:
+
+- Update the "Last Updated" date at the top of this policy
+- Notify registered users by email at least **14 days** before the changes take effect (for material changes affecting your rights)
+- Display a notice on minionry.com
+
+Your continued use of the Service after the effective date of a revised policy constitutes your acknowledgment of the changes. If you do not agree to the revised policy, you should discontinue use of the Service and may request deletion of your account.
+
+---
+
+## 17. Contact Us
+
+For privacy-related questions, data subject requests, or concerns about this policy:
+
+**Email:** onit@minionry.com
+**Website:** https://minionry.com
+
+**Minionry, Inc.**
+United States
+
+For formal data subject requests under GDPR or applicable law, please include "Privacy Request" in the subject line of your email.
+
+---
+
+*Copyright (c) 2025-present Minionry, Inc. All rights reserved.*

package/README.md

@@ -0,0 +1,57 @@
+# @minionry/minion
+
+Command-line client that connects this machine to your Minionry account.
+
+A Minionry account is required. Accounts are currently by invitation.
+
+## Requirements
+
+- Node.js 20.20+ or 22.22+
+
+## Install
+
+```bash
+npm i -g @minionry/minion
+```
+
+## Get started
+
+```bash
+cd path/to/your/project
+minion
+```
+
+The first run asks you to sign in. `minion` then keeps running in the
+background, and the folder appears at https://app.minionry.com.
+
+```bash
+minion status    # connection and sign-in status
+minion update    # update to the latest version
+minion --help    # all commands
+```
+
+## What it does on this machine
+
+- Keeps a connection to Minionry's servers open while it runs.
+- Reads and changes files and runs commands when you ask it to from your
+  Minionry account.
+- Checks those actions before they run and logs them locally under
+  `.minionry/logs/`.
+- Stores settings and credentials in `~/.minionry/`.
+
+See PRIVACY.md for what is sent where.
+
+## Telemetry
+
+Error reports and usage analytics are sent by default. To turn them off:
+
+```bash
+export MINIONRY_TELEMETRY=0
+```
+
+or set `"telemetry": false` in `~/.minionry/config/telemetry.json`.
+
+## License
+
+Proprietary. © Minionry, Inc. All rights reserved. Use is subject to the terms
+in LICENSE.

package/THIRD_PARTY_NOTICES.md

@@ -0,0 +1,245 @@
+# Third-party notices
+
+This package includes material from the following third-party projects, which
+are licensed under their own terms rather than the Minionry Commercial License.
+
+## fzf
+
+The fuzzy file-matching scorer in `dist/server/services/websocket/` is a port
+of the `FuzzyMatchV2` algorithm from https://github.com/junegunn/fzf.
+
+```
+The MIT License (MIT)
+
+Copyright (c) 2013-2026 Junegunn Choi
+
+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.
+```
+
+## moby/profiles
+
+`bin/sandbox/seccomp-userns.json` is derived from `seccomp/default.json` in
+https://github.com/moby/profiles, with one rule group added.
+
+Licensed under the Apache License, Version 2.0, reproduced below.
+
+---
+
+
+                                 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.