sim 1.0.17 → 2.0.0-dev.6.1

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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 2026 Sim Studio, Inc.
+
+   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.

package/README.md

@@ -1,92 +1,331 @@
-# Sim
+# Sim CLI
 
-Simple Node.js HTTP-server
+Talk to the [Sim](https://sim.ai) API from your terminal.
 
-## Styles
+```bash
+npm install --global sim
+sim login
+sim workflows list
+```
+
+Prerelease channels track the corresponding Sim environments:
+
+```bash
+npm install --global sim@staging # staging
+npm install --global sim@dev     # dev
+```
+
+## Profiles
+
+Profiles work like the AWS CLI: one identity and one set of defaults per named
+profile, selected with `-P`, `--profile`, or `SIM_PROFILE`. This is what lets you keep
+production and a local dev stack side by side without re-authenticating.
+
+Non-secret settings live in `~/.sim/config`:
+
+```ini
+[default]
+endpoint = https://sim.ai
+workspace = ws_abc123
+output = table
+
+[profile dev]
+endpoint = http://localhost:3000
+workspace = ws_local
+```
+
+Keys live in `~/.sim/credentials`, written `0600`:
+
+```ini
+[default]
+api_key = sim_…
+
+[dev]
+api_key = sim_…
+```
+
+The section-naming asymmetry — `[profile dev]` in config, `[dev]` in credentials
+— is the AWS convention, kept so existing habits and tooling carry over.
+
+```bash
+sim configure --set-endpoint http://localhost:3000 --profile dev
+sim configure --set-workspace ws_local --profile dev
+sim profiles          # list them; * marks the active one
+sim whoami            # resolved values, and where each came from
+```
+
+## Where settings come from
+
+Each setting resolves independently, first match wins:
+
+| Rank | Source |
+| --- | --- |
+| 1 | Command-line flag (`--endpoint`, `--workspace`, `--output`) |
+| 2 | Environment (`SIM_ENDPOINT`, `SIM_API_KEY`, `SIM_WORKSPACE`, `SIM_OUTPUT`) |
+| 3 | `~/.sim/config` / `~/.sim/credentials` for the selected profile |
+| 4 | Built-in default (`https://sim.ai`, `table`) |
+
+Formats are listed under [Output formats](#output-formats).
+
+`sim whoami` prints the winning source per setting, which is usually the fastest
+way to explain a surprising result.
+
+For CI, skip `sim login` entirely and set `SIM_API_KEY` and `SIM_WORKSPACE` —
+nothing needs to touch the filesystem. `SIM_CONFIG_DIR` relocates both files if
+you need to keep them somewhere other than `~/.sim`.
+
+## Logging in
+
+`sim login` uses the same browser handoff shape as `gh auth login`: the terminal
+prints a pairing code and a URL, you approve in a browser, and the key comes back
+over the CLI's own connection. Nothing redeemable crosses the browser leg, and
+there is no loopback listener — so it works over SSH and inside containers.
+
+```
+$ sim login --profile dev --endpoint http://localhost:3000
+
+Pairing code: K7M2-P9XT
+Confirm this code matches what the browser shows before approving.
+
+http://localhost:3000/cli/auth?request=…&scope=platform
+Waiting for approval…
+
+✓ Logged in. Key stored in /Users/you/.sim/credentials
+  Personal key, defaulting to ws_local. Override per command with --workspace.
+```
+
+The approval page is where you pick the workspace — the terminal has no key yet,
+so it cannot list them for you. `sim login` issues a personal key, and whichever
+workspace you pick becomes only the profile's default `workspace`; it does not
+limit the key to that workspace. Use `--workspace` to target another workspace
+the key can access.
+
+`sim login --workspace <id>` preselects a workspace in the picker, and an
+existing profile's workspace preselects itself on re-login.
+
+`sim logout` removes the stored key. It does not revoke it — do that in
+Settings → API keys.
+
+## Commands
+
+Plural resource names are canonical, but every plural top-level resource group
+also accepts its singular form: for example, `sim table list`,
+`sim file get`, and `sim workflow get` are equivalent to their plural
+spellings.
 
-### Block
+`knowledge` also accepts the shorter `kb` alias.
 
-```styl
+```bash
+sim workflows ls [path] [--search <text>] [--limit <n>]
+sim workflows list [--folder <path>] [--deployed-only] [--limit <n>]
+sim workflows get <id>
+sim workflows update <id> [--name <name>] [--description <text>] [--folder <path>]
+sim workflows mv <id> <folder>
+sim workflows deploy|undeploy|rollback <id>
+sim workflows run <id> [--input <json|@file>] [--select-output <path>…] [--async]
+sim workflows runs list --workflow <workflowId> [--status <status>]
+sim workflows runs get <runId> --workflow <workflowId> [--include-output]
+sim workflows runs cancel <runId> --workflow <workflowId>
+sim workflows runs resume <runId> --workflow <workflowId> --context <contextId> [--input <json|@file>]
 
-clear-box: all;
-clear-box: bounds;
-clear-box: position;
+sim logs list [--level error] [--workflow <id>…] [--trigger <name>…] [--start-date <date>]
+sim logs get <runId>
 
+sim audit-logs list --organization <organizationId> [--all-workspaces]
+sim audit-logs get <id> --organization <organizationId>
+
+sim workspaces get
+sim workspaces members
+
+sim tables ls [path] [--search <text>] [--limit <n>]
+sim tables list [--folder <path>]
+sim tables get <tableId>
+sim tables update <tableId> [--name <name>] [--description <text>] [--folder <path>]
+sim tables mv <tableId> <folder>
+sim tables columns <tableId>
+sim tables rows list <tableId> [--limit <n>]
+sim tables rows create <tableId> --data <json|@file>
+sim tables rows create <tableId> --rows <json|@file>
+sim tables rows query <tableId> [--filter <json>] [--sort <json>] [--limit <n>]
+sim tables rows query <tableId> --filter '{"all":[{"field":"status","op":"eq","value":"active"}]}'
+sim tables upsert <tableId> --data <json>
+sim tables rows batch-delete <tableId> (--row <id>… | --filter <json>) --yes
+
+sim files ls [path] [--search <text>] [--limit <n>]
+sim files list [--folder <path>]
+sim files describe <fileId>
+sim files get <fileId> [-o <path>]  # stdout by default
+sim files create --name <name> [--folder <path>] [--content <value>] [--encoding utf-8|base64]
+sim files upload <path> [--name <name>] [--folder <path>]
+sim files share get <fileId>
+sim files share set <fileId> --is-active <true|false> [--auth-type public|password|email|sso]
+sim files mv --file-ids <id>… [--to <path>]
+sim files batch-delete --file-ids <id>… --yes
+sim files delete <fileId> --yes
+
+sim knowledge ls [path] [--search <text>] [--limit <n>]
+sim knowledge list [--folder <path>]
+sim knowledge get <id>
+sim knowledge update <id> [--name <name>] [--description <text>] [--folder <path>]
+sim knowledge mv <id> <folder>
+sim knowledge search --query <text> --kb <id>… [--search-mode vector|hybrid]
+
+sim knowledge documents list <knowledgeBaseId> [--search <text>]
+sim knowledge documents get <knowledgeBaseId> <documentId>
+sim knowledge documents upload <knowledgeBaseId> <path> [--tag <value>...]
+sim knowledge documents delete <knowledgeBaseId> <documentId> --yes
+
+sim billing status [--all-workspaces]
+sim billing logs [--period 7d] [--source sim-chat] [--limit <n>] [--all-workspaces]
+```
+
+The `sim-chat` billing source combines Copilot and workspace chat usage.
+Organization audit logs require a personal API key. Commands with
+`--all-workspaces` otherwise default to the workspace in the active profile.
+
+`workflows runs get` is the lightweight status and polling resource.
+`--workflow` names the parent resource, while the run ID remains positional.
+For a paused run, its status includes the context ID needed by `resume`.
+`logs get` is the full diagnostic resource. It keeps the default human output
+concise; add `--trace` for the expanded recursive trace with span inputs,
+outputs, errors, timing, and cost. JSON and YAML retain the complete structured
+response.
+
+`sim logs get` keeps the default human output concise. Use JSON or YAML to
+inspect its complete `executionData` and recursive `traceSpans` tree:
+
+```bash
+sim logs get <runId> --trace
+sim logs get <runId> --output json | jq '.traceSpans'
+sim logs list --include-trace-spans --output json
+```
+
+Workflow output selectors use `blockName.field` syntax, such as
+`--select-output agent_1.content`; fields that are not produced are omitted.
+
+`ls` is a directory view: it combines the resources at its optional path with
+that folder's direct child folders. It never includes deeper descendants. Its
+`ref` column is the resource ID or canonical folder path to pass to the next
+command. Use `list` when you want resources only, or `folders ls` when you want
+folders only.
+
+Each folder-backed resource has the same path commands:
+
+```bash
+sim tables ls Reports
+sim tables folders ls --parent Reports
+sim tables mkdir Reports/Quarterly
+sim tables folders create Reports/Quarterly
+sim tables folders mv Reports/Quarterly Archive/Quarterly
+sim tables folders delete Archive/Quarterly --yes
+sim tables folders delete Archive --recursive --yes
+```
+
+`mkdir` is the concise form of `folders create`. Replace `tables` with `files`,
+`workflows`, or `knowledge`. The leading `/` is optional on API inputs; the API
+returns the canonical leading-slash form. Omit the `ls` path to list root.
+
+### List inputs
+
+Primitive lists take space-separated values. Prefix a path with `@` to read
+one value per line, or use `@-` to read the list from stdin.
+
+```bash
+sim files mv --file-ids file_1 file_2 --to Archive
+sim files mv --file-ids @file-ids.txt --to Archive
+printf 'file_1\nfile_2\n' | sim files mv --file-ids @- --to Archive
 ```
 
-### Util
+Arrays of objects remain JSON inputs because they cannot be represented as a
+flat list without losing structure.
 
-```styl
+### Filtering table rows
 
-selection: none;
-selection: text;
-selection: auto;
+`--filter` takes the same predicate tree the API uses — `all` (AND) or `any`
+(OR) groups of `{field, op, value}` conditions, nestable. It's JSON because the
+grammar is a tree; there's no honest flag encoding for it.
+
+```bash
+sim tables rows query tbl_123 \
+  --filter '{"all":[{"field":"status","op":"eq","value":"open"},
+                    {"field":"score","op":"gt","value":10}]}' \
+  --sort score:desc --limit 50
+```
 
-antialias: true;
-antialias: none;
+Row columns are discovered at runtime from the returned data, unioned across the
+page so a sparse row doesn't hide a column.
 
-bluring: 5px;
+Deletions require an explicit selector *and* `--yes`; there is no "delete
+everything" default.
 
-selection-background: #333;
-selection-color: #ccc;
+### Output formats
 
-clr: #999;
+Output format can be selected per command with `--output`, saved as a profile
+default with `sim configure --set-output <format>`, or set ambiently with
+`SIM_OUTPUT` for CI:
 
-+placeholder()
-  color: #ccc;
-  font-size: 16px;
+| Format | For |
+| --- | --- |
+| `table` | reading (default) |
+| `json` | piping into `jq` |
+| `yaml` | piping into anything that reads YAML |
+| `text` | shell loops — tab-separated, no header, no colour |
 
+`json` and `yaml` emit the API's **raw** values, not the table's formatting — a
+duration stays `1500`, not `"1.5s"` — so switching format never changes the data.
+`text` uses the rendered cells, since it is meant for shell plumbing rather than
+parsing.
+
+```bash
+sim configure --set-output json                      # for this profile, from now on
+sim configure --set-output text --profile scripts    # a profile dedicated to scripting
+
+sim --output json logs list --level error | jq -r '.[].runId'
+sim logs list --level error --output json | jq -r '.[].runId'
+SIM_OUTPUT=yaml sim logs list --level error > logs.yaml
+
+SIM_OUTPUT=text sim files list | while IFS=$'\t' read -r id name size type uploaded; do
+  echo "$id $name"
+done
 ```
 
-### Layout
-
-```styl
-lay: grid;
-lay: line;
-
-pin: center;
-pin: left;
-pin: right;
-pin: full;
-pin: mid;
-
-grav: top;
-grav: center;
-grav: bottom;
-grav: full;
-grav: text;
-
-side: pull;
-side: center;
-side: left;
-side: right;
-side: wide;
-side: mid;
-
-lane: single;
-lane: grid;
-lane: grid-reverse;
-
-way: right;
-way: left;
-way: down;
-way: up;
-
-order: 1;
-order: 4;
-
-rate: 1;
-rate: 3;
-
-reduce: 1;
-reduce: 2;
-
-size: 20%;
-size: auto;
-
-press: top;
-press: bottom;
-press: middle;
-press: pull;
-press: text;
+An absent value is an em-dash in `table` and an **empty field** in `text`, so
+emptiness tests downstream behave.
+
+An invalid active `SIM_OUTPUT` or `output =` value fails with the accepted
+formats. A valid higher-priority `--output` still overrides a stale lower tier,
+so `sim --output table configure --set-output json` can repair a profile.
+
+## How this stays in sync with the API
+
+`src/generated/v2-api.ts` is generated from the Zod route contracts in
+`apps/sim/lib/api/contracts/v2/**` — the same contracts the routes validate
+against, so a shape that disagrees with them is a shape the server would reject.
+It holds every response/request type plus the operation table (method, path,
+path params) the client dispatches through.
+
+```bash
+bun run generate:cli-api   # regenerate after changing a contract
+bun run check:cli-api      # CI: fails if the generated file is stale
+bun run check:openapi      # CI: fails if the docs and contracts disagree
 ```
+
+The generated file contains only type declarations and one const — no imports —
+so the `packages/*` must not import `apps/*` boundary is preserved; the script
+does the crossing at build time.
+
+The OpenAPI documents under `apps/docs` are deliberately **not** generated. They
+carry hand-written descriptions, examples, and error responses that Zod schemas
+don't encode, so regenerating them would trade real documentation for mechanical
+accuracy. `check:openapi` reconciles them against the same contracts instead —
+field by field, and it parses every documented example with the real Zod schema —
+so the prose survives while drift still fails the build.
+
+## Notes
+
+- Commands talk to the `/api/v2` surface, which returns `{ data }` and
+  `{ data, nextCursor }`. List commands auto-page up to `--limit`.
+
+## License
+
+Apache-2.0

package/THIRD_PARTY_LICENSES

@@ -0,0 +1,30 @@
+The Sim CLI bundle includes the following third-party software.
+
+chalk
+Copyright (c) Sindre Sorhus <sindresorhus@gmail.com> (https://sindresorhus.com)
+
+commander
+Copyright (c) 2011 TJ Holowaychuk <tj@vision-media.ca>
+
+js-yaml
+Copyright (C) 2011-2015 by Vitaly Puzrin
+
+Each dependency above is licensed under the MIT License:
+
+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.