vexpath 0.1.0__tar.gz

vexpath-0.1.0/.gitignore

@@ -0,0 +1,46 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+.eggs/
+build/
+dist/
+.venv/
+venv/
+
+# Tooling caches
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+.coverage.*
+htmlcov/
+coverage.xml
+
+# Local environment
+.env
+.env.local
+*.local.yml
+
+# Scan artefacts produced while dogfooding
+/sbom.cdx.json
+/openvex.json
+/cdx-vex.json
+/attestation.intoto.jsonl
+/results.json
+.vexpath-cache/
+
+# Advisory snapshots downloaded at runtime (the frozen test snapshot IS committed)
+/var/
+/data/
+
+# Editors and OS
+.vscode/
+.idea/
+*.swp
+.DS_Store
+Thumbs.db
+
+# Tailwind standalone binary (downloaded by `make tailwind-install`, not committed)
+/bin/tailwindcss
+/bin/tailwindcss.exe

vexpath-0.1.0/LICENSE

@@ -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 2026 Akmal Khan
+
+   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.

vexpath-0.1.0/PKG-INFO

@@ -0,0 +1,160 @@
+Metadata-Version: 2.5
+Name: vexpath
+Version: 0.1.0
+Summary: Command-line tool: generate SBOMs, match advisories, analyse reachability and emit signed VEX.
+Project-URL: Homepage, https://github.com/Unknown122-coder/vexpath
+Project-URL: Documentation, https://github.com/Unknown122-coder/vexpath/tree/main/docs
+Project-URL: Repository, https://github.com/Unknown122-coder/vexpath
+Project-URL: Issues, https://github.com/Unknown122-coder/vexpath/issues
+Project-URL: Changelog, https://github.com/Unknown122-coder/vexpath/releases
+Author: Akmal Khan
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: cyclonedx,openvex,reachability,sbom,sca,security,spdx,supply-chain,vex,vulnerability
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: System Administrators
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Security
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Topic :: System :: Software Distribution
+Classifier: Typing :: Typed
+Requires-Python: >=3.12
+Requires-Dist: rich>=13.9
+Requires-Dist: typer>=0.15
+Requires-Dist: vexpath-core==0.1.0
+Description-Content-Type: text/markdown
+
+# vexpath
+
+**Most of your vulnerability findings cannot run.** vexpath works out which
+ones can, and shows you the call path that proves it.
+
+```bash
+uv tool install vexpath      # or: pipx install vexpath
+vexpath scan .
+```
+
+A scanner tells you that `jinja2` has a critical advisory. vexpath reads the
+commit that fixed it, extracts the functions it changed, builds a call graph
+from your code through your dependencies, and tells you whether anything you
+run can reach them. On five real repositories it cleared 68 of 146 findings as
+unreachable, with the evidence for each.
+
+```
+SEVERITY  VERDICT       ADVISORY         COMPONENT              REACHABILITY
+--------------------------------------------------------------------------------
+HIGH      affected      CVE-2026-1234    jinja2 3.1.0           reachable_confirmed
+MEDIUM    not_affected  CVE-2026-5678    urllib3 2.2.1          unreachable
+
+38 findings | 10 reachable | 28 not affected | 0 under investigation
+```
+
+## What makes a finding clearable
+
+A finding is cleared only when the vulnerable code **provably** cannot run.
+That requires the dependency's own source, so:
+
+```bash
+pip install -e .            # or uv sync, or poetry install
+vexpath scan .
+```
+
+With nothing installed, vexpath still matches advisories but clears nothing —
+an absence of paths through code it never read proves nothing, and it says so
+rather than implying a clean bill of health. `--download-missing` fetches each
+dependency's source from the package index instead (nothing is executed,
+ever).
+
+## The gate
+
+```bash
+vexpath scan . --policy balanced
+```
+
+Exits 1 when a critical or high finding's vulnerable code is provably
+reachable, or when anything in your tree is in CISA's Known Exploited
+Vulnerabilities catalogue. Five presets, or write your own in CEL:
+
+```bash
+vexpath policy list
+vexpath scan . --policy 'findings.exists(f, f.kev && f.verdict != "not_affected")'
+```
+
+## Exit codes
+
+The contract with CI, and fixed:
+
+| Code | Meaning |
+|---|---|
+| 0 | Analysis completed and the policy passed |
+| 1 | Analysis completed and the policy **failed** — your dependencies need attention |
+| 2 | Analysis could not complete: a broken lockfile, an unreachable index |
+| 3 | Configuration error: a policy that does not compile, a bad flag |
+
+1 and 2 are separate on purpose. A build failing because the code is
+vulnerable must never look like a build failing because the tool broke.
+
+## What else it does
+
+| Command | What for |
+|---|---|
+| `vexpath scan` | The whole pipeline: SBOM → match → reachability → VEX → gate |
+| `vexpath reach --advisory CVE-…` | Why one verdict is what it is: symbols searched for, which entry points reach them, by what path, and the graph it rests on |
+| `vexpath report results.json --format sarif` | Re-render a scan. Nothing is re-analysed, so the SARIF matches the table |
+| `vexpath sbom generate` | CycloneDX 1.6 or SPDX 2.3 from seven lockfile formats |
+| `vexpath vex export` | OpenVEX 0.2.0 or CycloneDX VEX, with the evidence attached |
+| `vexpath attest sign` | A signed in-toto statement in a DSSE envelope, keyless or with a key |
+| `vexpath advisory sync` | Download a local advisory snapshot for offline and air-gapped use |
+| `vexpath policy test` | Try a gate against a scan that already ran |
+
+## Offline and reproducible
+
+```bash
+vexpath advisory sync --ecosystem PyPI --dir ./advisories
+vexpath scan . --snapshot ./advisories
+```
+
+A scan against a pinned snapshot can be re-derived. One against the live API
+cannot, and every report says which it was — a clearance nobody can reproduce
+is a claim, not a finding.
+
+## It never runs your dependencies
+
+Source is parsed with `ast`, never imported. `setup.py` is read, never
+executed. Archives are unpacked, never installed. A tool that executed what it
+analysed would be a worse supply-chain risk than the one it was looking for.
+
+## What it covers
+
+Advisory matching works for every ecosystem OSV publishes. **Reachability is
+Python only** — it is a real static analysis, not a heuristic, and one done
+properly for one language is worth more than four done badly. Lockfiles read:
+`uv.lock`, `poetry.lock`, `pdm.lock`, `Pipfile.lock`, `package-lock.json`,
+`pnpm-lock.yaml`, `requirements.txt` (pinned).
+
+`vexpath version` prints exactly what the build you have can do, because a
+cleared finding means nothing unless you know whether reachability ran.
+
+## In CI
+
+```yaml
+- uses: Unknown122-coder/vexpath@v1
+  with:
+    policy: balanced
+```
+
+The Action caches call graphs, writes SARIF for code scanning, and can comment
+on the pull request. A cold scan takes minutes; a warm one takes seconds.
+
+## Standards
+
+purl, OSV, CycloneDX 1.4–1.6, SPDX 2.2–2.3, OpenVEX 0.2.0, in-toto Statement
+v1, DSSE, Sigstore, SARIF 2.1.0, CVSS 3.x, PEP 440, semver, CEL.
+
+Apache 2.0.

vexpath-0.1.0/README.md

@@ -0,0 +1,128 @@
+# vexpath
+
+**Most of your vulnerability findings cannot run.** vexpath works out which
+ones can, and shows you the call path that proves it.
+
+```bash
+uv tool install vexpath      # or: pipx install vexpath
+vexpath scan .
+```
+
+A scanner tells you that `jinja2` has a critical advisory. vexpath reads the
+commit that fixed it, extracts the functions it changed, builds a call graph
+from your code through your dependencies, and tells you whether anything you
+run can reach them. On five real repositories it cleared 68 of 146 findings as
+unreachable, with the evidence for each.
+
+```
+SEVERITY  VERDICT       ADVISORY         COMPONENT              REACHABILITY
+--------------------------------------------------------------------------------
+HIGH      affected      CVE-2026-1234    jinja2 3.1.0           reachable_confirmed
+MEDIUM    not_affected  CVE-2026-5678    urllib3 2.2.1          unreachable
+
+38 findings | 10 reachable | 28 not affected | 0 under investigation
+```
+
+## What makes a finding clearable
+
+A finding is cleared only when the vulnerable code **provably** cannot run.
+That requires the dependency's own source, so:
+
+```bash
+pip install -e .            # or uv sync, or poetry install
+vexpath scan .
+```
+
+With nothing installed, vexpath still matches advisories but clears nothing —
+an absence of paths through code it never read proves nothing, and it says so
+rather than implying a clean bill of health. `--download-missing` fetches each
+dependency's source from the package index instead (nothing is executed,
+ever).
+
+## The gate
+
+```bash
+vexpath scan . --policy balanced
+```
+
+Exits 1 when a critical or high finding's vulnerable code is provably
+reachable, or when anything in your tree is in CISA's Known Exploited
+Vulnerabilities catalogue. Five presets, or write your own in CEL:
+
+```bash
+vexpath policy list
+vexpath scan . --policy 'findings.exists(f, f.kev && f.verdict != "not_affected")'
+```
+
+## Exit codes
+
+The contract with CI, and fixed:
+
+| Code | Meaning |
+|---|---|
+| 0 | Analysis completed and the policy passed |
+| 1 | Analysis completed and the policy **failed** — your dependencies need attention |
+| 2 | Analysis could not complete: a broken lockfile, an unreachable index |
+| 3 | Configuration error: a policy that does not compile, a bad flag |
+
+1 and 2 are separate on purpose. A build failing because the code is
+vulnerable must never look like a build failing because the tool broke.
+
+## What else it does
+
+| Command | What for |
+|---|---|
+| `vexpath scan` | The whole pipeline: SBOM → match → reachability → VEX → gate |
+| `vexpath reach --advisory CVE-…` | Why one verdict is what it is: symbols searched for, which entry points reach them, by what path, and the graph it rests on |
+| `vexpath report results.json --format sarif` | Re-render a scan. Nothing is re-analysed, so the SARIF matches the table |
+| `vexpath sbom generate` | CycloneDX 1.6 or SPDX 2.3 from seven lockfile formats |
+| `vexpath vex export` | OpenVEX 0.2.0 or CycloneDX VEX, with the evidence attached |
+| `vexpath attest sign` | A signed in-toto statement in a DSSE envelope, keyless or with a key |
+| `vexpath advisory sync` | Download a local advisory snapshot for offline and air-gapped use |
+| `vexpath policy test` | Try a gate against a scan that already ran |
+
+## Offline and reproducible
+
+```bash
+vexpath advisory sync --ecosystem PyPI --dir ./advisories
+vexpath scan . --snapshot ./advisories
+```
+
+A scan against a pinned snapshot can be re-derived. One against the live API
+cannot, and every report says which it was — a clearance nobody can reproduce
+is a claim, not a finding.
+
+## It never runs your dependencies
+
+Source is parsed with `ast`, never imported. `setup.py` is read, never
+executed. Archives are unpacked, never installed. A tool that executed what it
+analysed would be a worse supply-chain risk than the one it was looking for.
+
+## What it covers
+
+Advisory matching works for every ecosystem OSV publishes. **Reachability is
+Python only** — it is a real static analysis, not a heuristic, and one done
+properly for one language is worth more than four done badly. Lockfiles read:
+`uv.lock`, `poetry.lock`, `pdm.lock`, `Pipfile.lock`, `package-lock.json`,
+`pnpm-lock.yaml`, `requirements.txt` (pinned).
+
+`vexpath version` prints exactly what the build you have can do, because a
+cleared finding means nothing unless you know whether reachability ran.
+
+## In CI
+
+```yaml
+- uses: Unknown122-coder/vexpath@v1
+  with:
+    policy: balanced
+```
+
+The Action caches call graphs, writes SARIF for code scanning, and can comment
+on the pull request. A cold scan takes minutes; a warm one takes seconds.
+
+## Standards
+
+purl, OSV, CycloneDX 1.4–1.6, SPDX 2.2–2.3, OpenVEX 0.2.0, in-toto Statement
+v1, DSSE, Sigstore, SARIF 2.1.0, CVSS 3.x, PEP 440, semver, CEL.
+
+Apache 2.0.

vexpath-0.1.0/pyproject.toml

@@ -0,0 +1,68 @@
+[project]
+name = "vexpath"
+version = "0.1.0"
+description = "Command-line tool: generate SBOMs, match advisories, analyse reachability and emit signed VEX."
+readme = "README.md"
+requires-python = ">=3.12"
+license = "Apache-2.0"
+# A copy, not a reference to the root. A parent-directory path lands in
+# the source archive as `<name>-<version>/../../LICENSE`, which is a tar
+# member escaping its own root: newer uv refuses to read it outright, and
+# the archive was malformed regardless of which builder tolerated it. A
+# test asserts every copy is byte-identical to the root LICENSE.
+license-files = ["LICENSE"]
+authors = [{ name = "Akmal Khan" }]
+keywords = [
+    "security",
+    "sbom",
+    "vulnerability",
+    "reachability",
+    "sca",
+    "vex",
+    "openvex",
+    "cyclonedx",
+    "spdx",
+    "supply-chain",
+]
+# The PyPI page is where somebody decides whether to try this, so the
+# classifiers say what it is rather than only what it needs. "Development
+# Status :: 4 - Beta" is honest: the analysis is measured on real
+# repositories, and the hosted platform is new.
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Environment :: Console",
+    "Intended Audience :: Developers",
+    "Intended Audience :: System Administrators",
+    "License :: OSI Approved :: Apache Software License",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Security",
+    "Topic :: Software Development :: Quality Assurance",
+    "Topic :: System :: Software Distribution",
+    "Typing :: Typed",
+]
+
+dependencies = [
+    "vexpath-core==0.1.0",
+    "typer>=0.15",
+    "rich>=13.9",
+]
+
+[project.urls]
+Homepage = "https://github.com/Unknown122-coder/vexpath"
+Documentation = "https://github.com/Unknown122-coder/vexpath/tree/main/docs"
+Repository = "https://github.com/Unknown122-coder/vexpath"
+Issues = "https://github.com/Unknown122-coder/vexpath/issues"
+Changelog = "https://github.com/Unknown122-coder/vexpath/releases"
+
+[project.scripts]
+vexpath = "vexpath.main:app"
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/vexpath"]

vexpath-0.1.0/src/vexpath/__init__.py

@@ -0,0 +1,12 @@
+"""The ``vexpath`` command-line tool."""
+
+from __future__ import annotations
+
+from importlib.metadata import PackageNotFoundError, version
+
+try:  # pragma: no cover - depends on install mode
+    __version__ = version("vexpath")
+except PackageNotFoundError:  # pragma: no cover - running from a source tree
+    __version__ = "0.0.0+unknown"
+
+__all__ = ["__version__"]

vexpath-0.1.0/src/vexpath/commands/__init__.py

@@ -0,0 +1,3 @@
+"""Command implementations, one module per command group."""
+
+from __future__ import annotations