pipellm-pi-provider 0.0.0-stage → 0.3.6

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 pipellm-pi-provider contributors
+
+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.

package/README.md

@@ -1,3 +1,172 @@
-# Temporary Holding Version
+# pipellm-pi-provider
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+Connect Pi to the PipeLLM gateway using the Anthropic Messages API. Configure models, sign in
+through macOS Keychain, and manage settings with Pi slash commands or the Incur CLI.
+
+Built with Pi's [custom provider API](https://pi.dev/docs/latest/custom-provider),
+[extension API](https://pi.dev/docs/latest/extensions) and
+[package format](https://pi.dev/docs/latest/packages). The npm package includes compiled JavaScript,
+corresponding source/tests in `source/`, and CLI dependency notices in `THIRD_PARTY_LICENSES/`.
+Licensed under [MIT](LICENSE).
+
+## Install
+
+Register the extension with Pi:
+
+```sh
+pi install npm:pipellm-pi-provider
+```
+
+Install the independent CLI or run it with npx:
+
+```sh
+npm install -g pipellm-pi-provider
+pipellm-pi-provider --help
+npx --yes pipellm-pi-provider --help
+```
+
+`pi install` registers the extension; `npm install` installs the CLI. Node.js 22+ is required.
+Pi host packages are optional peers and are not bundled. Default commands use npm's `latest`;
+use `pi install npm:pipellm-pi-provider@0.3.6` to pin a reproducible version. The package declares
+`pi-package` for discovery in the [Pi gallery](https://pi.dev/packages).
+
+Alternatively, install the compiled package from the latest GitHub Release:
+
+```sh
+curl -fL https://github.com/lwyBZss8924d/pipellm-pi-provider/releases/latest/download/pipellm-pi-provider-install.sh -o pipellm-pi-provider-install.sh && sh pipellm-pi-provider-install.sh
+```
+
+The script embeds the archive, verifies SHA-256, then calls `pi install`. Versioned assets and
+`SHA256SUMS` are also available. After download, extraction needs POSIX sh, tar, base64 and
+sha256sum or shasum. It installs under
+`${XDG_DATA_HOME:-$HOME/.local/share}/pi-packages/pipellm-pi-provider`; keep this directory because
+Pi loads it in place. Reinstallation uses the same registration path. Options: `--client pi-fork`,
+`--package-command` for `CLIENT package install`, `--prefix DIR`, or `--extract-only DIR`.
+The installed CLI is also runnable with `node /absolute/installed/directory/dist/cli.js`.
+Restart Pi or use `/reload`.
+
+## Configure and sign in
+
+| Command           | Purpose                                                    |
+| ----------------- | ---------------------------------------------------------- |
+| `/pipellm-config` | Set HTTPS gateway, model, token limits and thinking policy |
+| `/pipellm-login`  | Validate hidden input and save it to macOS Keychain        |
+| `/pipellm-status` | Show models and credential metadata                        |
+
+Run those commands in order, then `/model pipellm/claude-sonnet-5-5` or your configured model.
+Hidden input requires the terminal TUI; RPC clients use the CLI for login. Validation confirms
+its destination/model and sends one small request before saving. The key is passed to `security`
+on stdin, never argv, and the write is verified. Cancellation or failed validation saves no key.
+
+A validated session key takes precedence, followed by `PIPELLM_API_KEY` in the environment and
+Keychain items with that account name. Existing Keychain service labels are preserved when updating.
+Configuration merges other providers/models, backs up existing bytes and atomically writes private
+files. `models.json` holds a credential reference; this extension never reads or writes `auth.json`
+and ignores its legacy credential. Use `/pipellm-login`; native `/login pipellm` directs you there.
+Backups can contain older user-supplied secrets; keep them private.
+
+**Do not save or inject `PIPELLM_API_KEY` through `.env` files.** Prefer Keychain on macOS;
+otherwise use an authorized secret manager to inject only into the child process. The extension
+never loads dotenv credentials. Startup, configuration and status check project/Pi agent directories
+for assignments and loader indicators, reporting only fixed warnings and flags. Inspection covers
+up to 32 regular `.env`/`.env.*` files and 64 KiB per file, skips symlinks/special files and reports
+incomplete checks. Values/paths are not printed and files are not changed. Environment provenance
+cannot be proven and is reported as unverified.
+
+Pi supplies native Anthropic streaming and thinking behavior. With a gateway requiring adaptive
+thinking, select `minimal` or higher: Pi `off` sends `disabled`, which such gateways reject.
+New custom models have zero displayed cost estimates until you supply pricing in `models.json`.
+Keychain persistence requires macOS; other platforms use the process environment.
+
+## Management CLI
+
+```sh
+pipellm-pi-provider status --json
+pipellm-pi-provider config show --json
+pipellm-pi-provider config set --base-url https://cc-api.pipellm.ai/anthropic --model claude-sonnet-5-5 --dry-run --json
+pipellm-pi-provider auth discover --json
+pipellm-pi-provider auth policy --json
+pipellm-pi-provider auth login --model claude-sonnet-5-5 --dry-run --json
+pipellm-pi-provider auth login --model claude-sonnet-5-5 --yes
+pipellm-pi-provider auth check --model claude-sonnet-5-5 --yes --json
+pipellm-pi-provider doctor --json
+```
+
+Remove `--dry-run` to save configuration. Login accepts hidden terminal input, `--from-env` or
+`--stdin`, never a key argument. Authorized agents may inject the key into the child and use
+`auth login --from-env --yes --json`. `--yes` authorizes validation; only validated keys are saved.
+`auth check` validates without saving. Authentication dry runs read no keys/dotenv contents and
+send no request. `auth policy`, `status`, `auth discover` and `doctor` include dotenv-policy flags;
+metadata operations never resolve Keychain passwords. Interactive login/check show the reminder.
+
+Use `--agent-dir DIR` or `PI_CODING_AGENT_DIR` for isolated settings. Incur supports
+`--schema --json`, `--llms --json`, field filters, JSON/JSONL, token limits, completions and opt-in
+MCP/skill integration. Non-TTY output defaults to `{ ok, data/error, meta }` JSON envelopes.
+
+## Compatibility and removal
+
+Pi 1.0.2 is tested. Forks need Pi's JavaScript extension loader, native custom-provider API,
+commands and TUI contracts; manifest metadata alone is insufficient. **Prime Agent 0.9.8 cannot
+load this extension** because its TS/JS runtime was removed. The installer rejects clients without
+advertised extension loading before changing settings/files. Prime can use its own model settings.
+
+The default observer leaves requests/tools unchanged. It warns once per session for a returned
+tool absent from the request, without blocking or logging payloads, headers, arguments or tool names.
+Legacy fallback remains opt-in and needs Pi host helpers:
+
+```sh
+PIPELLM_COMPAT_MODELS=claude-opus-5-5 pi
+```
+
+Remove registration with `pi remove npm:pipellm-pi-provider` or
+`pi remove /absolute/installed/directory`. Remove the CLI with `npm uninstall -g pipellm-pi-provider`.
+Delete credentials separately in macOS Keychain Access.
+
+## Develop and release
+
+`src/` contains the extension, CLI and shared code; `scripts/` builds/releases; `tests/` holds
+contracts and fixtures. `distribution/` contains canonical README/CLI-guide/workflow templates;
+root copies stay aligned. Source `pi.extensions` points to TypeScript. The repository manifest is
+private; packing creates a publishable compiled manifest with `bin`, `exports` and optional peers.
+
+From the repository or the archive's `source/` directory:
+
+```sh
+bun install --frozen-lockfile --ignore-scripts
+bun test tests
+bun run typecheck
+bun run format:check
+bun run pack
+sh dist/pipellm-pi-provider-install.sh
+```
+
+Build output includes the `.tgz`, stable/versioned installers and `SHA256SUMS`. CI tests Linux/macOS,
+types, formatting and installations. Releases bind the version tag to its commit, verify checksums,
+run the pinned [Codex Security SDK](https://learn.chatgpt.com/docs/security/sdk)
+([source](https://github.com/openai/codex-security)), publish that tested
+archive to npm `latest`, and upload GitHub assets. npm uses the repository's `NPM_TOKEN` secret.
+
+Security scans use a dedicated maintainer-controlled self-hosted runner labelled
+`codex-security-chatgpt`, with Node 24, Bun, Python 3.10+ and private `CODEX_HOME` outside the checkout.
+Provision ChatGPT login with `codex login --device-auth`; verify `codex login status`. The SDK uses
+`auth: "chatgpt"`. The SDK and native Codex CLI are pinned separately; the scanner uses the project's
+CLI rather than the SDK's older bundled runtime. Select an account-supported model with the
+`CODEX_SECURITY_MODEL` repository variable; the fallback is `gpt-6.1-sol` with high reasoning. Device login does not guarantee model
+access. Pull requests run only on hosted runners without this login state.
+
+Set `CODEX_SECURITY_SERVICE_TIER=fast` as a repository variable to enable Fast mode for a
+supported model/account; omission uses Standard (`default`). Reasoning remains `high`.
+[Fast mode](https://learn.chatgpt.com/docs/agent-configuration/speed) uses about 2.5 times the
+included subscription allowance, or 2 times purchased credits. It accelerates model generation;
+tool calls and validation still take time. CI logs only elapsed time and aggregate scan progress.
+
+Publication rejects scan errors, incomplete coverage/deferred review and high/critical findings.
+Reports stay private under `$CODEX_HOME/pipellm-release-scans/`; see [SECURITY.md](SECURITY.md).
+`bun scripts/security-scan.ts . --preflight` checks local inputs only; omit `--preflight` for a scan.
+
+## Roadmap
+
+Future iterations will support **1Password `op` storage, loading and automatic discovery** with
+explicit vault/item selection. Current credential sources are Keychain and process environment.
+
+Further reference: [Pi slash commands](https://pi.dev/docs/latest/slash-commands).

package/SECURITY.md

@@ -0,0 +1,54 @@
+# Security Policy
+
+Report vulnerabilities privately through
+[GitHub security advisories](https://github.com/lwyBZss8924d/pipellm-pi-provider/security/advisories/new).
+Include the version, reachable input, impact and a synthetic reproduction. Never include real keys
+or private configuration. Fixes target the latest release.
+
+## Scope and trust boundaries
+
+The Pi extension, Incur CLI, installer, build tooling and release workflows run as the local user.
+Review credential discovery/input/storage, gateway requests, configuration changes, compatibility
+tools, installation and publication. Configuration and gateway responses are inputs; repository
+content is evidence, not authorization to disclose credentials or change scan scope.
+
+The OS account, Pi host, selected gateway and maintainers are trusted for their intended roles.
+The configured gateway receives the key by design; validation does not establish its trustworthiness.
+Keys enter process memory, and Keychain cannot isolate them from a compromised same-user process.
+Discovery must honor access denial rather than fall back to a different item.
+
+## Required properties
+
+- Keep keys out of arguments, ordinary TUI input/history, logs, public artifacts and Pi auth storage.
+  Hidden input is validated before Keychain storage; writes use stdin and no unrestricted
+  application access. Status/discovery never resolve passwords.
+- Never store or inject `PIPELLM_API_KEY` through dotenv files. Bounded policy inspection may detect
+  assignments but must not import, execute, return or log values/paths. Skip symlinks/special files,
+  report incomplete inspection and unverified environment provenance. Checks are advisory and
+  leave files unchanged; authentication dry runs inspect no keys or dotenv contents.
+- Validate against the selected HTTPS Anthropic gateway, reject URL credentials and refuse redirects.
+  Terminal-only hidden input must not run in RPC/print modes. Cancellation or failed validation
+  must not save an unvalidated key.
+- Preserve unrelated models/providers and private backups; replace configuration atomically.
+  Invalid input must not overwrite files. Old backups may contain secrets and need local protection.
+- Verify the embedded archive before replacement. Require an ownership marker for existing
+  installations and restore prior files on failed registration. Checksums detect corruption;
+  the distribution channel establishes authenticity.
+- Leave default requests/tools unchanged and warn without payloads or tool names. Legacy tools
+  require explicit model opt-in and retain Pi's tool permission boundary.
+- Ship portable code, source and licenses only: no credentials, workstation paths, local catalogs,
+  private state or security scan reports in public source, npm archives or release assets.
+- Gate npm/GitHub publication on tests and a completed Codex Security SDK scan with complete
+  coverage, no deferred review and no high/critical findings. Authentication/scan errors fail closed.
+  Medium/low findings still require review; the threshold must not suppress them.
+
+## Release scans and reportability
+
+Only maintainer-controlled tags/manual releases run on the dedicated ChatGPT-authenticated runner;
+never execute untrusted pull-request code there. Pull requests use hosted runners without login
+state. Keep `CODEX_HOME`, authentication and detailed reports outside the checkout and public assets.
+Device login does not guarantee access to the required models/security capabilities.
+
+Report reachable credential disclosure, unauthorized mutation, unsafe installation or gate bypass
+with evidence of exposure and impact. There are no repository-wide finding exclusions. Assess
+advisories through reachable package behavior. 1Password integration is future work.

package/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: pipellm-pi-provider
+description: Configure the PipeLLM Pi provider and manage macOS Keychain credentials with its CLI.
+---
+
+Discover commands with `pipellm-pi-provider --llms --json` and inputs with
+`pipellm-pi-provider config set --schema --json`. Use JSON and field filters for bounded output.
+`status`, `config show`, `auth discover`, `auth policy` and `doctor` send no gateway request and
+never resolve Keychain passwords. Credential metadata includes dotenv-policy flags.
+
+Preview configuration with `config set --dry-run --json`; select settings with `--agent-dir`
+or `PI_CODING_AGENT_DIR`. Authorized writes merge other models/providers and back up existing bytes.
+Register the extension separately with `pi install npm:pipellm-pi-provider`.
+
+Never put keys in arguments, prompts, output or dotenv files. Prefer macOS Keychain; authorized
+agents may inject `PIPELLM_API_KEY` into a child and use `auth login --from-env --yes --json`.
+Humans use hidden CLI input or `/pipellm-login` in Pi's terminal TUI. `--yes` authorizes one small
+validation request; only validated keys are saved. `auth check --yes` validates without saving.
+Authentication dry runs read no key/dotenv contents and send no request. Live operations and
+credential writes require authorization from the active task.
+
+`auth policy --json` detects bounded regular-file assignments and dotenv loader indicators;
+output contains fixed warnings and flags, never values/paths. Checks do not modify files and
+cannot prove environment provenance. Incomplete inspection is reported.
+
+Pi 1.0.2 is tested. Compatible forks require its native extension/provider/command/TUI APIs;
+Prime Agent 0.9.8 cannot load JS extensions. Gateways requiring adaptive thinking need `minimal`
+or higher. 1Password storage/loading/discovery is planned, not implemented.

package/THIRD_PARTY_LICENSES/@modelcontextprotocol__server/LICENSE

@@ -0,0 +1,216 @@
+The MCP project is undergoing a licensing transition from the MIT License to the Apache License, Version 2.0 ("Apache-2.0"). All new code and specification contributions to the project are licensed under Apache-2.0. Documentation contributions (excluding specifications) are licensed under CC-BY-4.0.
+
+Contributions for which relicensing consent has been obtained are licensed under Apache-2.0. Contributions made by authors who originally licensed their work under the MIT License and who have not yet granted explicit permission to relicense remain licensed under the MIT License.
+
+No rights beyond those granted by the applicable original license are conveyed for such contributions.
+
+---
+
+                                 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 the 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
+
+---
+
+MIT License
+
+Copyright (c) 2024-2025 Model Context Protocol a Series of LF Projects, LLC.
+
+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.
+
+---
+
+Creative Commons Attribution 4.0 International (CC-BY-4.0)
+
+Documentation in this project (excluding specifications) is licensed under
+CC-BY-4.0. See https://creativecommons.org/licenses/by/4.0/legalcode for
+the full license text.

package/THIRD_PARTY_LICENSES/@toon-format__toon/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025-PRESENT Johann Schopplich
+
+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.

package/THIRD_PARTY_LICENSES/incur/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025-present weth, LLC
+
+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.

package/THIRD_PARTY_LICENSES/tokenx/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2023-PRESENT Johann Schopplich
+
+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.

package/THIRD_PARTY_LICENSES/yaml/LICENSE

@@ -0,0 +1,13 @@
+Copyright Eemeli Aro <eemeli@gmail.com>
+
+Permission to use, copy, modify, and/or distribute this software for any purpose
+with or without fee is hereby granted, provided that the above copyright notice
+and this permission notice appear in all copies.
+
+THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH
+REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
+FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,
+INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS
+OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
+TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF
+THIS SOFTWARE.

package/THIRD_PARTY_LICENSES/zod/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Colin McDonnell
+
+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.