speja 0.14.0__py3-none-win_amd64.whl

speja/__init__.py

@@ -0,0 +1,29 @@
+"""speja: a VHDL formatter and style checker with VSG-compatible rules and configuration.
+
+The package ships the ``speja`` executable. :func:`find_speja_bin` returns its path, for
+tools that want to run it without relying on ``PATH``.
+"""
+
+from __future__ import annotations
+
+import os
+import sys
+import sysconfig
+
+__all__ = ["find_speja_bin"]
+
+
+def find_speja_bin() -> str:
+    """Return the path of the ``speja`` executable installed with this package."""
+    exe = "speja.exe" if sys.platform == "win32" else "speja"
+    candidates = [
+        sysconfig.get_path("scripts"),
+        sysconfig.get_path("scripts", scheme=sysconfig.get_preferred_scheme("user")),
+        # `pip install --target <dir>` puts scripts in `<dir>/bin`.
+        os.path.join(os.path.dirname(os.path.dirname(os.path.abspath(__file__))), "bin"),
+    ]
+    for directory in candidates:
+        path = os.path.join(directory, exe)
+        if os.path.isfile(path):
+            return path
+    raise FileNotFoundError(f"could not find {exe} in {candidates}")

speja/__main__.py

@@ -0,0 +1,22 @@
+"""``python -m speja``: run the bundled ``speja`` executable."""
+
+from __future__ import annotations
+
+import os
+import subprocess
+import sys
+
+from speja import find_speja_bin
+
+
+def main() -> int:
+    exe = find_speja_bin()
+    if sys.platform == "win32":
+        # `exec` does not replace the process on Windows; forward the exit code instead.
+        return subprocess.run([exe, *sys.argv[1:]], check=False).returncode
+    os.execv(exe, [exe, *sys.argv[1:]])
+    return 0  # unreachable
+
+
+if __name__ == "__main__":
+    sys.exit(main())

speja-0.14.0.dist-info/METADATA

@@ -0,0 +1,307 @@
+Metadata-Version: 2.4
+Name: speja
+Version: 0.14.0
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: Microsoft :: Windows
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Programming Language :: Rust
+Classifier: Topic :: Scientific/Engineering :: Electronic Design Automation (EDA)
+Classifier: Topic :: Software Development :: Quality Assurance
+License-File: LICENSE-MIT
+License-File: LICENSE-APACHE
+License-File: THIRD_PARTY_LICENSES.md
+Summary: Catch VHDL bugs before simulation: a fast Rust formatter and linter with VSG-compatible rules and configuration.
+Keywords: vhdl,formatter,linter,vsg,fpga
+License-Expression: MIT OR Apache-2.0
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown; charset=UTF-8; variant=GFM
+Project-URL: Documentation, https://github.com/ru551n/speja/tree/main/docs
+Project-URL: Repository, https://github.com/ru551n/speja
+
+<p align="center">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/ru551n/speja/main/docs/assets/speja-logo-dark.png">
+    <img src="https://raw.githubusercontent.com/ru551n/speja/main/docs/assets/speja-logo.png" alt="" width="128">
+  </picture>
+</p>
+
+# speja
+
+[![CI](https://github.com/ru551n/speja/actions/workflows/ci.yml/badge.svg)](https://github.com/ru551n/speja/actions/workflows/ci.yml)
+[![Documentation](https://readthedocs.org/projects/speja/badge/?version=latest)](https://speja.readthedocs.io/)
+[![PyPI](https://img.shields.io/pypi/v/speja)](https://pypi.org/project/speja/)
+[![License](https://img.shields.io/badge/license-MIT%20OR%20Apache--2.0-blue)](#licence)
+
+**Catch it earlier. Earlier than simulation.**
+
+A VHDL formatter and linter in Rust. Every bug has a price that goes up the longer it takes to
+find: a moment in your editor, a coffee in CI, an afternoon in a waveform viewer, a respin on
+silicon. speja moves what it can to the cheap end of that scale: the moment you save the file.
+
+Some of what it reports a simulator would have told you eventually: an index outside its array,
+a value outside its subtype, a process that can never suspend. *Eventually* means after you have
+written the testbench, elaborated the design and waited for the run, and only if the run reaches
+that line. Some of it no simulator will ever tell you, because the design elaborates perfectly
+well and simply does not mean what it says.
+
+It runs the rule set, command line and configuration of the
+[VHDL Style Guide](https://vhdl-style-guide.readthedocs.io/) (VSG), adds a formatter that fixes
+what it reports, and adds a lint layer that VSG has no equivalent of.
+
+A default lint run reports **definite errors only**: things that cannot work, rather than things
+worth a look. Everything that depends on what you meant is one line of configuration away.
+
+**Status: beta.** The style layer implements VSG 3.35's rule set and is tested against more than
+11,000 real-world files; expect layout changes before 1.0. The lint layer (`speja lint`) is
+newer and its rule set is still growing.
+
+## Install
+
+```sh
+pip install speja            # Linux, Windows and macOS wheels, Python 3.10+
+uv tool install speja        # or
+cargo install --path .        # from source (Rust 1.95 or newer)
+```
+
+Standalone binaries for Linux (static, x86_64 and aarch64), Windows (x64 and arm64) and macOS
+(arm64 and x86_64) are attached to each
+[release](https://github.com/ru551n/speja/releases), with a `SHA256SUMS` file.
+
+## Everything VSG accepts, unchanged
+
+```sh
+speja -f src/*.vhd -c vsg.yaml --fix
+```
+
+The arguments, the configuration file, the reports and the exit codes are VSG's, and
+[VSG documents them](https://vhdl-style-guide.readthedocs.io/en/latest/usage.html). Existing
+scripts and CI jobs keep working, so this README covers only what speja adds on top.
+Differences are listed in
+[compatibility](https://speja.readthedocs.io/en/latest/compatibility/).
+
+## What speja adds
+
+**A real formatter.** Source is parsed once into a lossless syntax tree and printed in one
+canonical layout, like rustfmt or Black. Every layout rule is fixed rather than reported, long
+lines are folded at structural boundaries, and running `--fix` twice changes nothing. All
+violations are reported at once and fixed in a single pass: no repeated runs, no rule-order
+dependencies.
+
+**Safety.** Formatted output is re-parsed and must contain exactly the same tokens and comments;
+files with syntax errors are never changed. Fixes VSG does not apply by default need
+`--unsafe_fixes`.
+
+**Speed.** Real-world VHDL is checked at about 3.4 MB/s on one core, in parallel worker
+processes.
+
+### Beyond style: `speja lint`
+
+Rules that need names resolved, which a per-file style checker cannot do:
+
+```sh
+speja lint --recursive src                  # the lint layer
+speja --recursive src --check style,lint    # both in one run
+```
+
+```
+lint_600 -- Signal 'flag' is not assigned on every path of this combinational process,
+            which infers a latch
+lint_601 -- Signal 'result' is assigned by 2 concurrent statements (lines 34, 38)
+lint_001 -- The signal 'b' is not read in the sensitivity list (first read at line 10)
+```
+
+Sensitivity lists, unused declarations, latch inference, multiple drivers, combinational loops,
+state machines, vector widths, clock-domain crossings, and the type and name diagnostics of a
+real front end. Every rule states the evidence behind it and reports nothing when that evidence
+is missing.
+
+Most of these resolve names across files, which needs a library map. Without one they are
+skipped, and the run says so. See
+[static analysis](https://speja.readthedocs.io/en/latest/lint/) and
+[project setup](https://speja.readthedocs.io/en/latest/project-setup/).
+
+### Adopting a rule set on existing code
+
+```sh
+speja --recursive src --generate_waivers waivers.yaml   # accept what exists today
+speja --recursive src --waivers waivers.yaml            # from now on, only new violations
+```
+
+[Waivers](https://speja.readthedocs.io/en/latest/waivers/) record a rule, a file glob, lines and
+a reason, and never affect the exit code.
+
+### Options speja adds
+
+| Option | Meaning |
+|---|---|
+| `lint`, `--check style,lint` | run the lint layer, or both layers |
+| `--lint_configuration FILE` (`-lc`) | configuration for the lint layer only |
+| `--waivers`, `--generate_waivers`, `--show_waived` | accept known violations |
+| `--unsafe_fixes` | also apply fixes VSG does not apply by default; review the result |
+| `--diff` | with `--fix`, print a unified diff instead of changing files |
+| `--range START:END` | with `--fix`, change only these lines |
+| `--stdin_filename PATH` | name of the `--stdin` input, for configuration lookup and reports |
+| `--sarif FILE` | SARIF 2.1.0, for GitHub code scanning |
+| `--sonarqube FILE` | SonarQube generic issue JSON |
+| `--recursive` | check the VHDL files in directories and their subdirectories |
+| `--list_rules`, `--statistics` | what each rule is, and how often each fired |
+
+Configuration keys speja adds live under a `speja:` block: `reflow_comments`,
+`testbench_files`, `testbench_libraries`, `synchronizers`, and a `rule:` block per kind of
+file.
+
+### Editors and coding agents
+
+Two servers over stdio, both the same engine as the command line, so everything is told the same
+thing about the same file under the same configuration.
+
+```sh
+speja lsp                        # a language server: diagnostics, formatting, quick fixes
+speja mcp                        # an MCP server, for a coding agent
+```
+
+The [language server](https://speja.readthedocs.io/en/latest/lsp/) is meant to run beside
+`vhdl_ls` rather than instead of it, and advertises only what speja is: it answers no
+completion, hover or definition request. A [VS Code extension](editors/vscode/README.md) ships
+it, and adds [editing actions](https://speja.readthedocs.io/en/latest/vscode-editing/) built on
+VHDL-LS, such as instantiating an entity and declaring a port map's signals. Those need VHDL-LS
+running; lint and format do not.
+
+The [MCP server](https://speja.readthedocs.io/en/latest/mcp/) gives a coding agent three tools,
+`lint`, `format` and `explain_rule`:
+
+```sh
+claude mcp add speja -- speja mcp
+```
+
+```json
+{ "mcpServers": { "speja": { "command": "speja", "args": ["mcp"] } } }
+```
+
+`lint` and `format` take a file path or a buffer. A buffer is how an agent checks what it is
+about to write before writing it, which is one step earlier still; `format` with `write` fixes a
+file in place without moving it through the conversation.
+
+For Claude Code there is a plugin, which installs a `vsg` skill and registers the MCP server:
+
+```text
+/plugin marketplace add ru551n/speja
+/plugin install speja@speja
+```
+
+The skill tells an agent to format and check VHDL before committing it, how to read a finding's
+class, and not to treat a run that skipped the library map as a clean file. `speja` itself still
+has to be on `PATH`.
+
+### CI
+
+A [GitHub Action](https://speja.readthedocs.io/en/latest/github-action/) posts annotations and
+suggested changes; [GitLab CI](https://speja.readthedocs.io/en/latest/gitlab-ci/) gets the
+code-quality report, and SonarQube the generic issue JSON. Jenkins reads the SARIF file through
+Warnings-NG. Every [report format](https://speja.readthedocs.io/en/latest/reports/) works
+anywhere.
+
+```yaml
+- uses: ru551n/speja@v0.14.0
+  with:
+    args: --recursive src
+```
+
+## Documentation
+
+**[speja.readthedocs.io](https://speja.readthedocs.io/)**: what speja adds on top of VSG. The
+rules, their options and the configuration file are VSG's own and are linked to rather than
+repeated.
+
+* [Quick start](https://speja.readthedocs.io/en/latest/quick-start/)
+* [Static analysis](https://speja.readthedocs.io/en/latest/lint/) and
+  [project setup](https://speja.readthedocs.io/en/latest/project-setup/)
+* [Rule reference](https://speja.readthedocs.io/en/latest/rule-reference/)
+* [Running in an airgap](https://speja.readthedocs.io/en/latest/airgapped/): what it needs, what
+  it cannot reach, and how to check both yourself
+* [Language server](https://speja.readthedocs.io/en/latest/lsp/),
+  [MCP server](https://speja.readthedocs.io/en/latest/mcp/) and
+  [Claude Code plugin](https://speja.readthedocs.io/en/latest/claude-code/)
+* [Waivers](https://speja.readthedocs.io/en/latest/waivers/)
+* [Migrating from VSG](https://speja.readthedocs.io/en/latest/migrating-from-vsg/)
+* [Compatibility with VSG](https://speja.readthedocs.io/en/latest/compatibility/), measured
+  weekly against two corpora
+
+## Disclosure: this code was written by an LLM
+
+Most of this repository was written by Claude, directed and reviewed by a human. Treat that as a
+reason to check it rather than a reason to trust it, so here is what there is to check against.
+None of it depends on the code having been written well.
+
+**It cannot reach anything.** No network, proven four ways in CI on every change: no dependency
+is an HTTP or TLS client, the binary imports no symbol that can reach a host, everything runs
+inside an empty network namespace, and `strace` records zero network syscalls. You can run those
+same checks against the binary you downloaded in about five minutes:
+[running in an airgap](https://speja.readthedocs.io/en/latest/airgapped/).
+
+**It cannot quietly mangle your files.** Formatted output is re-parsed and must contain exactly
+the same tokens and comments, in the same order, before anything is written. A mismatch is an
+internal error and your file is left untouched, so a formatter bug costs you a run rather than a
+file. Files with syntax errors are never modified, writes are atomic through a temporary file in
+the same directory, and a file whose output equals its input is not rewritten at all.
+
+**Its blast radius is small.** `#![forbid(unsafe_code)]`. No privileges, no service, no daemon,
+no telemetry. The only state it keeps is a 2.3 MB cache of the embedded `ieee` and `std` sources,
+written once per version. The only time it starts another program is `--local_rules`, which runs
+the VSG on your `PATH`, because only VSG can run VSG's Python plugins.
+
+**It is checked against reality, not against itself.** The formatter is compared with VSG's own
+output over a corpus of real VHDL, weekly. Every lint rule must report nothing on three real
+projects unless a person has confirmed each finding is a genuine defect, and those counts are a
+CI gate. Fuzzing runs nightly. Agreement is
+[published per rule](https://speja.readthedocs.io/en/latest/compatibility/) rather than claimed.
+
+**Known limits, stated rather than buried.** A dependency (`vhdl_lang`) can stack-overflow on
+pathological input, which aborts the process before anything is written. A file you made
+read-only is still replaced, because atomic writes need permission on the directory rather than
+on the file. Both are in the
+[airgap page](https://speja.readthedocs.io/en/latest/airgapped/).
+
+Cautious first run? `--fix --diff` changes nothing and prints what it would do, `--backup` keeps
+a copy beside each file, and a run without `--fix` never writes anything at all.
+
+## Relationship to VSG
+
+> **speja is an independent Rust implementation of a VHDL formatter and style checker that aims
+> for compatibility with the rules and configuration of the VHDL Style Guide (VSG). It is not
+> affiliated with, endorsed by, or maintained by the VHDL Style Guide project or its
+> maintainers.**
+>
+> speja was inspired by the
+> [VHDL Style Guide (VSG)](https://github.com/jeremiah-c-leary/vhdl-style-guide) project by
+> Jeremiah Leary and contributors. speja contains no VSG code; VSG is used only as a behavioural
+> reference.
+
+Every release states the VSG version it targets, and `speja --version` prints it.
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for the build, test and corpus commands, how compatibility
+is measured, and what CI runs.
+
+## Licence
+
+Either [Apache License, Version 2.0](LICENSE-APACHE) or [MIT](LICENSE-MIT), at your option.
+Third-party dependencies are listed in [THIRD_PARTY_LICENSES.md](THIRD_PARTY_LICENSES.md) and in
+[NOTICE](NOTICE); the VHDL parser, `vhdl_syntax` from the rust_hdl project, is MPL-2.0 and is
+used as an unmodified dependency.
+
+Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in
+speja, as defined in the Apache-2.0 license, shall be dual licensed as above, without any
+additional terms or conditions.
+

speja-0.14.0.dist-info/RECORD

@@ -0,0 +1,10 @@
+speja/__init__.py,sha256=WAOm2j79e2mMbfaSwFYAQKv-OZE-Ny6N7QDQ-RIDRAU,1060
+speja/__main__.py,sha256=k4XWHvHOIScov1bKnCxv_7yQkVr-MRPtzsC7n8ZDo4Y,560
+speja-0.14.0.data/scripts/speja.exe,sha256=NBsUsmJ7Gm5TlFDRjz05JnWBwoN7Jc6rWEuUi99XIBU,14280192
+speja-0.14.0.dist-info/METADATA,sha256=Fq9u3eM98--8ok_j1G3XjaMQQW3nA5YctKjGzpSMOLw,15106
+speja-0.14.0.dist-info/WHEEL,sha256=8Aej0W0a6Cz6apA3IzJrTnxLRVLAt-w0Oh8SA3Con_c,94
+speja-0.14.0.dist-info/licenses/LICENSE-APACHE,sha256=fP1zjFPWHHnwfjSPYiv3cHyQhCNwVNN_vgd4inX1iBw,11048
+speja-0.14.0.dist-info/licenses/LICENSE-MIT,sha256=5nogDSWJW1DjZ0BXlg0yBRghqctrwvo8c5w14pio-pM,1091
+speja-0.14.0.dist-info/licenses/THIRD_PARTY_LICENSES.md,sha256=5YRm9Gpf9ZeFis2Vu1rzBgj6enSa-B_k6w-hPfdjqM4,9276
+speja-0.14.0.dist-info/sboms/speja.cyclonedx.json,sha256=UUykkZjLSJq8LNmeGHcsoWUxssidhed33AqEDJJgmDw,130274
+speja-0.14.0.dist-info/RECORD,,

speja-0.14.0.dist-info/WHEEL

@@ -0,0 +1,4 @@
+Wheel-Version: 1.0
+Generator: maturin (1.15.0)
+Root-Is-Purelib: false
+Tag: py3-none-win_amd64

speja-0.14.0.dist-info/licenses/LICENSE-APACHE

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

speja-0.14.0.dist-info/licenses/LICENSE-MIT

@@ -0,0 +1,25 @@
+Copyright (c) 2026 The speja 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.