@n8r/surface 0.0.0-stage → 0.1.0-experimental.5

package/plugins/n8r-surface/skills/research/references/skeleton-surface.md

@@ -0,0 +1,105 @@
+# Skeleton Surface v0.1
+
+This is a provisional output profile within the AI Surface Model. Produce a
+compact Markdown Surface working draft, not validated JSON/HTML or a deployment
+recipe. The profile version describes these rules; the skill version identifies
+the instructions used. Neither is the revision of the particular Surface/setup.
+
+## Select and bound the brief
+
+Use this profile when asked for a skeleton or brief Surface. Broad discovery
+starts shallow; a narrow question takes precedence over a general inventory.
+Security is the focus of this profile, while the model supports other purposes.
+The useful question is: where could a security integration inspect or intervene
+in LLM and actual tool calls, with what powers, coverage and gaps?
+
+Retain a node or distinction when removing it hides a key capability, a material
+security boundary, or a place an Experiment could change or observe behavior.
+Keep required supporting roles such as application persistence when they explain
+the setup. Features can be capability nodes; do not turn every setting into a node.
+Use a role such as MCP server or vector store when no instance is selected. Source
+evidence may identify supported products/transports without identifying a binding.
+An empty template field does not establish that every deployment lacks a binding.
+
+Preserve stable node and relationship identities from supplied descriptions.
+Different serialization or vocabulary requires an explicit mapping, not silent
+renaming. Keep shared nodes, parallel routes and cycles. A historical claim not
+re-established at the selected revision must stay qualified or move to a clearly
+linked historical/gap record; it cannot become a current supported capability.
+
+## Keep the graph small without losing meaning
+
+Lead with a short identity/scope line and a graph or edge table. Retain source
+revision, Surface revision and profile name/version. Show key nodes, directed
+relationships, purposes and relevant execution/authority boundaries. Label
+supported possibilities separately from selected composition and observed setup.
+No source-only graph establishes reachability or exercise.
+
+Use concise claim references to linked research or source sections. Identify the
+supporting revision and locator where available. Summarize coverage and unresolved
+questions once where shared; retain exceptions beside the affected edge. Avoid
+repeating boilerplate unknown bindings for every node, but never make an omitted
+value imply absence. No arbitrary node count, depth ceiling or file-size minimum
+applies. A smaller output is not permission to discard a condition or bypass.
+
+| In the brief | In linked records |
+| --- | --- |
+| Nodes, directed edges, roles, material conditions and uncertainty | Detailed source excerpts, inspected ranges and investigation narrative |
+| Claim basis and usable evidence references | Full provenance, conflicts and supporting findings |
+| Interception location, visibility, powers and coverage gaps | Hook signatures, configuration details and vendor compatibility research |
+| Binding status and reference when relevant | Protected resource bindings, nonsecret configuration and secret requirements/references |
+| Observation summary with applicability, when supplied | Dated runtime observations, traces, tests and Experiment Run results |
+
+Use existing evidence records when they suffice. Do not create a large companion
+record just to satisfy a template; direct versioned source references can suffice.
+Keep links portable or state which accompanying files are needed. Never invent
+records or imply their contents were read. Credential values do not belong in
+the brief or research evidence.
+
+## Map interception opportunities
+
+For each relevant candidate, state compactly:
+
+- **Location and stage:** node/edge, before/after model dispatch or tool execution.
+- **Visible context:** messages, tool arguments/results, principal, or unknown.
+- **Powers:** observe, modify, block or require approval, only as supported.
+- **Coverage:** covered routes, conditions, bypasses and unresolved continuations.
+- **Basis:** proposed placement, documented/implemented extension, configured
+  integration, or exercised behavior; link evidence and preserve its limits.
+
+A proxy only sees traffic routed through it. Seeing tool schemas, model-proposed
+calls or returned results in model traffic does not prove mediation of the actual
+tool invocation or downstream effects. Trace the tool executor separately. Keep
+browser-direct routes, scheduled workers and other known alternate paths visible.
+
+A hook's presence does not establish its timing, veto power or complete coverage.
+A sidecar is placement, not an interception mechanism: identify routing, hooks or
+event delivery and how a decision reaches execution. Observation-only telemetry
+is not enforcement. Record failure behavior if known, or as a gap relevant to
+later setup selection; a documented claim is not a runtime test.
+
+Record potential cross-service observation points and correlation gaps without
+claiming end-to-end trace coverage. Do not select a vendor or infer product
+compatibility from names or protocols. If evidence supports only an opportunity,
+say so. Stop once the brief answers the question with gaps visible. Do not install,
+bind resources, configure proxies/hooks or run integration tests as part of it.
+
+## Continue and reconcile
+
+Size and deployment knowledge are independent. A bound setup can have a skeleton;
+a detailed product description can remain unbound. When saving or continuing,
+follow [working notes](working-notes.md), preserving predecessors and evidence.
+
+For Lab-managed changes, the intended consumer behavior is to record a successor
+setup/binding revision with the change and its evidence; an Experiment requests
+resources from its Lab, which owns bindings. This skill does not implement that
+automation. A request is not proof that configuration succeeded. Keep effective
+setup unknown until supported by observation.
+
+Changes outside the Lab do not automatically update saved descriptions. On an
+explicit reconciliation request, read current identified evidence, compare it
+with the predecessor and save an authorized successor. Preserve stable identities,
+explain changed declarations/bindings and retain uncertainty about effective use.
+Reference an unchanged definition when only bindings change; use a successor
+definition when composition or intended settings change. Keep profile version
+unchanged unless the output rules change. Do not retrospectively rebind prior Runs.

package/plugins/n8r-surface/skills/research/references/working-notes.md

@@ -0,0 +1,121 @@
+# Working research notes
+
+Use Markdown for the first portable research increment. These are readable
+working notes, not a released interchange schema or a validated experimental
+HTML/Surface artefact. Use the user's requested prose format when practical;
+retain the same evidence and limitations. Do not impose a large empty template.
+
+## Where notes live
+
+Use a user-selected destination first. For work explicitly scoped to a recognized
+Surface workspace, keep new notes under `research/<source-slug>/` within that
+workspace, creating directories only on an authorized save. Do not redirect that
+work to a global vault or the default below. When continuing a supplied note,
+retain its folder unless the user asks to move it. Workspace setup itself creates
+no notes or content directories. When an applicable vault convention places
+Surface descriptions under `surfaces/<source-slug>/`, propose a numbered file
+such as `surface-draft-001.md` there. A save offer does not create directories or
+files; wait for acceptance. Without that convention, use the default below for
+the same Markdown working draft. When continuing a saved note, use its
+folder unless the user requests a move. Otherwise, on a host with a persistent
+user-owned local filesystem, use:
+
+```text
+~/Documents/n8r-surface/research/<source-slug>/<topic>-001.md
+```
+
+Derive short lowercase hyphenated slugs from the source and question. For a
+LibreChat authentication investigation, use `librechat/authentication-001.md`.
+Resolve the user's actual home directory through the host, expand `~`, and show
+the absolute folder and filename before writing. Create missing directories as
+part of an authorized save. Keep that local locator in the conversation, not in
+portable note content. Do not treat a temporary execution container as the user's
+persistent filesystem. If local saving is unavailable, explain that limitation
+and offer a named Markdown download or text without claiming the default exists.
+
+List existing notes for that topic first. Use the next unused three-digit number
+(`002`, `003`, and so on; grow beyond three digits if needed). An existing filename
+is never permission to overwrite. For continuation, read the predecessor and any
+human edits, name it in the successor and record the change. Recheck its bytes
+before saving; if they changed, reread and reconcile before choosing a new output.
+Check that existing notes describe the same source before continuing them;
+matching directory names alone do not establish source identity.
+
+Provide the actual saved file as a clickable link after readback. On a local
+host, use an absolute file link. The user should be able to open it without
+searching the plugin cache or scrolling back through tool output. Skill removal
+must leave this research folder and every previous note intact.
+
+## What a note retains
+
+A saved note should let another person or a fresh chat continue the task:
+
+- Identify the question, scope, date, skill version and host/tool capabilities
+  actually used. Do not guess a hidden model ID or application version.
+- Identify the supplied sources using portable relative names or public locators.
+  Record available revision/version information and exact hashes for inspected
+  files when supported. Explicitly mark unavailable identity evidence.
+- Lead with the partial AI Surface graph or edge table, stable component labels
+  and evidence locations. Keep supported possibilities separate from selected
+  connections. Include only settings needed to explain the graph, not an app-wide
+  configuration inventory.
+- Preserve conflicting claims, unknowns, coverage limits and scoped absences.
+- Retain human decisions and unanswered questions separately from source evidence.
+- State what was actually read or exercised and what remains to be done. Include
+  **Recommended next steps** as described below, and a useful next question when
+  a user decision is needed.
+
+Keep source links usable when the notes are moved, or explain what accompanying
+source files are needed. Do not copy whole repositories or credentials into the
+notes. A source digest identifies bytes, not truth, completeness or compatibility.
+
+## Recommended next steps
+
+Include a **Recommended next steps** section in the latest Surface note for the
+same source and scope. If no Surface note exists, include it in the latest research
+note. A Surface note here is a saved prose description of the Surface; this rule
+does not add validated structured-output support or require creating one.
+
+For each recommendation, state:
+
+- **Next investigation:** the concrete question or connection to investigate.
+- **Why it matters:** which uncertainty or user decision it would resolve.
+- **Where to resume:** the relevant source file/section, component ID, saved note
+  or permitted view, plus any access or missing evidence needed to proceed.
+
+Use portable references, not local absolute paths or credentials. For example:
+
+> **Next investigation:** establish the selected document-search target.
+> **Why it matters:** the optional search path has no address in the supplied
+> settings, so its selected connection remains unresolved.
+> **Where to resume:** `current.env`, `DOCUMENT_SEARCH_URL`, and `system.md` →
+> Uploaded documents; request applicable deployment settings if available.
+
+When continuing, read this section alongside the predecessor and human edits,
+re-establish source identity, and use it to choose the next investigation within
+the user's current scope. Recommendations are proposed work, not permission for
+new access or evidence that a connection exists. If the needed evidence is
+unavailable, retain the blocker and a concrete resumption point.
+
+In the saved successor, update the section to reflect what was resolved, what
+remains and the next useful investigation. Explain a changed priority or superseded
+recommendation briefly. Preserve earlier notes unchanged. If an older note has
+no recommendations, derive them from its supported gaps and current evidence in
+the successor; do not retrofit the predecessor. If no further investigation is
+needed within scope, say so and explain why rather than inventing work.
+
+## Save and read back
+
+If the destination already exists or changed since it was read, stop that write
+and propose a new file or a reviewed merge. Do not claim atomic guarded storage
+or byte-conflict guarantees that the host has not provided.
+
+After saving, read the saved bytes through an available tool and check that the
+findings, references, uncertainties, human choices and current recommendations
+survived. Provide the actual path or download and report any readback limitation. Merely printing a filename
+is not a save. Reopening in a fresh chat is a separate continuation check.
+
+Installing or removing the skill changes its availability in the host. User notes
+belong to the user and must remain outside the plugin installation/cache folders.
+Never delete research as part of skill removal. Uninstallation does not erase
+instructions or source content already present in an old conversation.

package/plugins/n8r-surface/skills/research/references/workspace.md

@@ -0,0 +1,89 @@
+# Workspace operations
+
+Use this mode for setup, repeated setup, readiness and fresh-chat recognition.
+A workspace is a user-owned folder, independent of a vault, source checkout,
+Lab or app project. The only initial file is `.n8r/workspace.json`.
+
+If the user means starting research in a web Project rather than creating a local
+folder, use [first-use access](first-use-access.md) and begin from supplied sources.
+If explicit local setup is requested but the host cannot access a persistent local
+filesystem or supported Node runtime, report that operation blocked. Keep useful
+source research available; do not ask for a laptop path the host cannot access.
+
+## Run the shared helper
+
+Requires a local persistent filesystem and Node.js 22, 24 or 26 on macOS/Linux.
+Use the helper **from this installed skill**, resolving its absolute path relative
+to this reference, not from a developer checkout. Invoke it through `node`:
+
+```sh
+node /installed/skill/scripts/workspace.mjs inspect /selected/workspace
+node /installed/skill/scripts/workspace.mjs setup /selected/workspace --purpose 'Investigate LibreChat'
+```
+
+The paths above are placeholders. Quote actual paths and supplied text safely;
+never interpolate untrusted metadata into shell code. `inspect` only reads.
+`setup` requires the user's explicit setup request. Supply `--name` only if the
+user supplied a display name; otherwise the folder name is used. Supply a brief
+nonsecret `--purpose` from the stated intent when available; it is optional.
+Do not put credentials, private bindings or absolute source paths in metadata.
+No naming/schema questionnaire is needed. Ask for a destination only when the
+user's selected/current folder cannot be established.
+
+If Node, the helper, local access or persistent storage is unavailable, explain
+that blocker and the concrete prerequisite. Do not install a runtime, recreate
+the helper's filesystem logic by hand, or claim a download is a local workspace.
+A host without shell/local persistence cannot perform this workspace operation.
+The standalone research CLI and Labs do not yet expose this capability.
+
+## Interpret the result
+
+The helper prints one JSON object with `status`, `message`, absolute `directory`
+when available, and `record` for a supported workspace. Exit 0 means created or
+recognized; exit 3 means missing, empty or awaiting a destination choice; exit 2
+means invalid input, malformed/unsupported metadata, conflict or I/O failure.
+These are helper results, not permission to expand the task.
+
+- `created`: report the actual location and a useful next research action. The
+  helper has read back the complete record. No research has started.
+- `recognized`: reuse the saved ID, name and optional purpose without rewriting
+  or asking again. Report readiness for research, not proof of prior research or
+  a configured target. For a readiness question, offer a next action based on
+  saved purpose or relevant existing notes without starting it. Read notes only
+  as needed; do not infer findings from metadata or generic filenames.
+- `missing` / `empty`: inspection found no workspace. Explain this; recognition
+  alone does not authorize creation. An explicit setup request can call `setup`.
+- `needs-choice`: explain that files already exist and ask “Initialize here, or
+  use another folder?” Make no writes before the choice. Only an explicit
+  initialize-here choice permits `setup PATH --adopt` (with supplied name/purpose).
+  If another folder is chosen, run normal setup there without `--adopt`.
+- `malformed` / `unsupported` / `conflict`: explain the helper's specific reason
+  and offer another destination or separately requested repair assessment. Make
+  no changes; no automatic migration, downgrade, replacement or cleanup.
+- `invalid-input` / `io-error`: report the specific limitation; do not claim
+  success. An interrupted operation may leave metadata staging files. Inspect
+  read-only if needed; repair is separate and never implied by a retry.
+
+For recognized/created results, identify the saved format and stable ID without
+requiring the user to understand their encoding. Keep the interaction short.
+Filesystem creation does not attach the folder to an app project. Say attachment
+is separate; only claim it if a supported host action actually occurred. Setup
+does not require attachment, Git, credentials, global settings or a vault.
+Do not create README, AGENTS.md, `.gitkeep`, models or content directories during
+setup. Research remains a separate requested action.
+
+## Shared metadata meaning
+
+`n8r.workspace/1` is independent of plugin and AI Surface Model versions. The
+helper validates a JSON object with that exact `format`, generated UUID v4 `id`,
+nonempty text `name`, and optional text `purpose`. Unknown fields are preserved
+and confer no capabilities. The ID survives setup repetition, rename, move and
+fresh sessions. Invalid JSON/required fields are malformed; a different format
+token is unsupported. Recognition is always read-only, never repair.
+
+The bundled `scripts/workspace.mjs` exports `validateWorkspace`,
+`inspectWorkspace` and `setupWorkspace` for future consumers. It owns the
+filesystem decisions; do not fork them into host-specific implementations.
+It publishes complete metadata without overwriting a target. Interrupted staging
+is never accepted as a valid record. Concurrent writers, adversarial filesystem
+mutation, migration and power-loss durability are not supported guarantees.

package/plugins/n8r-surface/skills/research/scripts/THIRD-PARTY-NOTICES.txt

@@ -0,0 +1,273 @@
+Bundled third-party code and schemas
+
+CycloneDX 1.7 schemas: OWASP Foundation / CycloneDX contributors, Apache-2.0.
+Source commit 4b3f59453366e27c8073fd24e98bf21ef8892c8e. See bundled LICENSE for Apache-2.0 terms.
+
+ajv 8.20.0 (MIT)
+The MIT License (MIT)
+
+Copyright (c) 2015-2021 Evgeny Poberezkin
+
+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.
+
+
+
+ajv-formats 3.0.1 (MIT)
+MIT License
+
+Copyright (c) 2020 Evgeny Poberezkin
+
+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.
+
+
+ajv-formats-draft2019 1.6.1 (MIT)
+MIT License
+
+Copyright (c) 2020 Carlo Q
+
+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.
+
+
+extend 3.0.2 (MIT)
+The MIT License (MIT)
+
+Copyright (c) 2014 Stefan Thomas
+
+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.
+
+
+
+fast-deep-equal 3.1.3 (MIT)
+MIT License
+
+Copyright (c) 2017 Evgeny Poberezkin
+
+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.
+
+
+fast-uri 3.1.9 (BSD-3-Clause)
+Copyright (c) 2011-2021, Gary Court until https://github.com/garycourt/uri-js/commit/a1acf730b4bba3f1097c9f52e7d9d3aba8cdcaae
+Copyright (c) 2021-present The Fastify team <https://github.com/fastify/fastify#team>
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+    * Redistributions of source code must retain the above copyright
+      notice, this list of conditions and the following disclaimer.
+    * Redistributions in binary form must reproduce the above copyright
+      notice, this list of conditions and the following disclaimer in the
+      documentation and/or other materials provided with the distribution.
+    * The names of any contributors may not be used to endorse or promote
+      products derived from this software without specific prior written
+      permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS AND CONTRIBUTORS BE LIABLE FOR ANY
+DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+                                  *   *   *
+
+The complete list of contributors can be found at:
+- https://github.com/garycourt/uri-js/graphs/contributors
+
+json-schema-traverse 1.0.0 (MIT)
+MIT License
+
+Copyright (c) 2017 Evgeny Poberezkin
+
+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.
+
+
+nearley 2.20.1 (MIT)
+The MIT License (MIT)
+
+Copyright (c) 2014, 2015, 2016, 2017, 2018, 2019 Kartik Chandra, Tim Radvan
+
+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.
+
+
+schemes 1.4.0 (MIT)
+
+(The MIT License)
+
+Copyright (c) 2015 Peter Müller <munter@fumle.dk>
+
+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.
+
+
+smtp-address-parser 1.1.1 (MIT)
+MIT License
+
+Copyright (c) 2021 Gene Hightower
+
+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.
+
+
+uri-js 4.4.1 (BSD-2-Clause)
+Copyright 2011 Gary Court. All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
+
+1.	Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
+
+2.	Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
+
+THIS SOFTWARE IS PROVIDED BY GARY COURT "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL GARY COURT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+The views and conclusions contained in the software and documentation are those of the authors and should not be interpreted as representing official policies, either expressed or implied, of Gary Court.
+
+
+yaml 2.9.1 (ISC)
+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.