aetherx-reprocert 0.2.2a1__py3-none-any.whl

aetherx_reprocert-0.2.2a1.dist-info/METADATA

@@ -0,0 +1,373 @@
+Metadata-Version: 2.5
+Name: aetherx-reprocert
+Version: 0.2.2a1
+Summary: Claim-to-evidence reproducibility certificates for software, AI and research workflows.
+Project-URL: Homepage, https://github.com/AETHERXGLOBAL/reprocert
+Project-URL: Documentation, https://github.com/AETHERXGLOBAL/reprocert/tree/main/docs
+Project-URL: Issues, https://github.com/AETHERXGLOBAL/reprocert/issues
+Project-URL: Source, https://github.com/AETHERXGLOBAL/reprocert
+Author: AETHER X GLOBAL
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: attestation,ci,evidence,provenance,reproducibility,verification
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+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: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.11
+Requires-Dist: pyyaml<7,>=6.0.2
+Provides-Extra: dev
+Requires-Dist: build<2,>=1.2; extra == 'dev'
+Requires-Dist: pytest<10,>=8.3; extra == 'dev'
+Description-Content-Type: text/markdown
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/AETHERXGLOBAL/.github/main/profile/assets/aether-x-premium-banner.png" alt="AETHER X GLOBAL" width="100%" />
+</p>
+
+<h1 align="center">ReproCert</h1>
+
+<p align="center"><strong>Claim-to-evidence reproducibility certificates for software, AI and research workflows.</strong></p>
+
+<p align="center">
+  <a href="https://github.com/AETHERXGLOBAL/reprocert/actions/workflows/ci.yml"><img alt="CI" src="https://github.com/AETHERXGLOBAL/reprocert/actions/workflows/ci.yml/badge.svg"></a>
+  <a href="./LICENSE"><img alt="License: Apache-2.0" src="https://img.shields.io/badge/License-Apache--2.0-blue.svg"></a>
+  <img alt="Python 3.11+" src="https://img.shields.io/badge/Python-3.11%2B-blue.svg">
+  <img alt="Status: Public Alpha" src="https://img.shields.io/badge/Status-Public%20Alpha-orange.svg">
+</p>
+
+<p align="center">
+  <code>CLAIM → EXACT COMMAND → EVIDENCE → VERDICT → CERTIFICATE</code>
+</p>
+
+---
+
+## What ReproCert does
+
+ReproCert is an open-source developer tool from **AETHER X GLOBAL** that turns explicit technical claims into machine-checkable, reproducible evidence records.
+
+Instead of writing an unsupported statement such as:
+
+> “This benchmark completes in under two seconds.”
+
+you define the claim, command, evidence files and acceptance conditions. ReproCert executes the declared workflow, records evidence and environment metadata, evaluates the checks, and emits a machine-readable certificate with one of four explicit outcomes:
+
+`PASS` · `FAIL` · `INCONCLUSIVE` · `ERROR`
+
+ReproCert is intentionally narrow. It does **not** claim that a benchmark is unbiased, a scientific hypothesis is true, or software is secure merely because a certificate passes.
+
+`CERTIFICATE INTEGRITY ≠ PRODUCER AUTHENTICITY ≠ SCIENTIFIC TRUTH`
+
+## Why it exists
+
+Modern software and AI projects routinely publish performance, compatibility, reproducibility and data-quality claims. The evidence behind those claims is often fragmented across scripts, CI logs, screenshots and human interpretation.
+
+ReproCert creates a portable boundary between a claim and its supporting execution evidence:
+
+```text
+CLAIM
+  ↓
+DECLARED EXECUTION
+  ↓
+OBSERVED EVIDENCE
+  ↓
+EXPLICIT CHECKS
+  ↓
+PASS / FAIL / INCONCLUSIVE / ERROR
+  ↓
+REPRODUCIBILITY CERTIFICATE
+```
+
+It is designed to complement — not replace — test frameworks, benchmark harnesses, SLSA, in-toto, Sigstore, GitHub Artifact Attestations and experiment-tracking systems.
+
+## Looking for early adopters
+
+Have a real CI, benchmark, testing, AI, or research workflow where a technical claim should be backed by portable evidence?
+
+**ReproCert is actively looking for early adopters.**
+
+Good first integrations include:
+
+- pytest or JUnit quality gates;
+- benchmark thresholds;
+- reproducible build or artifact checks;
+- data-quality assertions;
+- CI policies that require explicit evidence;
+- workflows that would benefit from signed provenance.
+
+You do **not** need to redesign your project around ReproCert. The preferred first integration is small, isolated, and reversible.
+
+**[Open an Adoption / Integration request →](https://github.com/AETHERXGLOBAL/reprocert/issues/new?template=adoption.yml)**
+
+You can also read the public adopter call in [Issue #7](https://github.com/AETHERXGLOBAL/reprocert/issues/7).
+
+## Quickstart — self-service
+
+No AETHER X account, API key, hosted service, or approval is required.
+
+Until the first PyPI publication is completed, install the stable v0.2 channel directly from GitHub:
+
+```bash
+python -m pip install "git+https://github.com/AETHERXGLOBAL/reprocert.git@v0.2"
+```
+
+Initialize a pytest project and generate a GitHub Actions workflow:
+
+```bash
+reprocert init pytest --github-actions
+reprocert doctor
+reprocert run reprocert.yml -o reprocert-certificate.json
+reprocert verify reprocert-certificate.json --claim reprocert.yml --evidence-root .
+```
+
+For other workflows:
+
+```bash
+reprocert init command --github-actions
+reprocert init benchmark --github-actions
+```
+
+Or run `reprocert init --github-actions` and let ReproCert conservatively detect pytest.
+
+Expected result:
+
+```text
+ReproCert verdict: PASS
+```
+
+See the [5-Minute Start](docs/QUICKSTART_5_MIN.md) and [Troubleshooting](docs/TROUBLESHOOTING.md).
+
+## Example claim
+
+```yaml
+apiVersion: reprocert.dev/v1alpha1
+kind: ReproducibilityClaim
+metadata:
+  id: api-latency
+  title: Median latency stays below the declared threshold
+spec:
+  command: [python, benchmark.py]
+  timeout_seconds: 60
+  evidence:
+    - results.json
+  checks:
+    - id: latency
+      source:
+        type: json
+        path: results.json
+        pointer: /median_ms
+      op: lt
+      expected: 2000
+```
+
+### Supported observation sources
+
+`json` · `text` · `stdout` · `stderr` · `exit_code` · `file_sha256` · `file_size` · `junit`
+
+### Supported comparators
+
+`eq` · `ne` · `lt` · `le` · `gt` · `ge` · `approx` · `contains`
+
+## Verdict semantics
+
+| Verdict | Meaning |
+|---|---|
+| **PASS** | Execution completed as specified, required evidence was available, and every declared check passed. |
+| **FAIL** | Execution completed, evidence was available, and at least one declared claim check was false. |
+| **INCONCLUSIVE** | Execution completed but required evidence could not be resolved or adjudicated. |
+| **ERROR** | The declared execution could not run as specified, timed out, or returned an unexpected process exit code. |
+
+The distinction matters: a crashed benchmark is not automatically evidence that the benchmark claim is false.
+
+## GitHub Action
+
+Use ReproCert directly in another repository:
+
+```yaml
+- uses: AETHERXGLOBAL/reprocert@v0.2
+  id: reprocert
+  with:
+    claim: path/to/claim.yml
+    certificate: reprocert-certificate.json
+
+- run: |
+    echo "Verdict: ${{ steps.reprocert.outputs.verdict }}"
+    echo "Digest: ${{ steps.reprocert.outputs.certificate-digest }}"
+```
+
+For untrusted pull requests, use least-privilege workflow permissions and never expose secrets to code you do not trust.
+
+## Multi-claim suites
+
+ReproCert v0.2 can execute several independent claims under one aggregate report while preserving a separate certificate for every member claim.
+
+```bash
+reprocert suite examples/suite.yml \
+  --output suite-report.json \
+  --certificate-dir .reprocert/certificates
+```
+
+A known false claim remains `FAIL`; it is not hidden by an unrelated execution error. See [Claim Suites](docs/SUITES.md).
+
+## JUnit integration
+
+Existing test systems can feed ReproCert without rewriting their test runners. Point a check at JUnit XML and select an aggregate metric:
+
+```yaml
+source:
+  type: junit
+  path: junit.xml
+  metric: failures
+op: eq
+expected: 0
+```
+
+Supported metrics are `tests`, `failures`, `errors`, `skipped`, `passed`, and `time_seconds`. See [JUnit Integration](docs/JUNIT.md).
+
+## Pytest-native adapter
+
+Projects that already use pytest can create a ReproCert certificate directly:
+
+```bash
+reprocert pytest --workdir . --output pytest-certificate.json -- -q
+```
+
+The adapter preserves pytest semantics: ordinary test failures become ReproCert `FAIL`, while unexpected pytest execution states remain `ERROR`. See [Pytest-Native Adapter](docs/PYTEST.md).
+
+## Hardened container execution profile
+
+A claim may run through a constrained Docker profile using an immutable image digest:
+
+```yaml
+container:
+  engine: docker
+  image: registry.example/tool@sha256:<64-hex-digest>
+  network: none
+  read_only_root: true
+  drop_capabilities: true
+  no_new_privileges: true
+```
+
+Mutable image tags are rejected. The profile is continuously exercised on GitHub-hosted Ubuntu, but it is **not** described as a proof of deterministic computation. See [Container Profile](docs/CONTAINER_PROFILE.md).
+
+## Certificate policy layer
+
+Organizations can apply acceptance requirements without rewriting the underlying claim verdict:
+
+```bash
+reprocert policy certificate.json policy.yml -o policy-result.json
+```
+
+A certificate may remain `PASS` while the policy result is `FAIL` because, for example, CI or container execution was required. Policy evaluation verifies certificate integrity first. See [Policy Layer](docs/POLICY.md).
+
+## Custom attestation predicate
+
+Generate a privacy-minimized predicate from a certificate:
+
+```bash
+reprocert predicate certificate.json -o reprocert-predicate.json
+```
+
+The reference workflow signs both general artifact provenance and the ReproCert-specific predicate with GitHub Artifact Attestations. The predicate deliberately excludes command text and stdout/stderr excerpts.
+
+## Certificate verification
+
+ReproCert separates two questions:
+
+1. **Is the certificate internally consistent with the claim and evidence I have?**  
+   `reprocert verify` checks certificate integrity, verdict consistency, optional claim identity and optional evidence hashes.
+
+2. **Who produced the certificate and in which repository/workflow?**  
+   Use a signed external attestation. This repository includes a reference workflow using GitHub Artifact Attestations.
+
+A certificate self-digest is a stable content identifier. It is **not** a digital signature.
+
+## Developer surface
+
+- [Architecture](docs/ARCHITECTURE.md)
+- [Attestation model](docs/ATTESTATION.md)
+- [Claim suites](docs/SUITES.md)
+- [JUnit integration](docs/JUNIT.md)
+- [Pytest-native adapter](docs/PYTEST.md)
+- [Container profile](docs/CONTAINER_PROFILE.md)
+- [Policy layer](docs/POLICY.md)
+- [5-minute start](docs/QUICKSTART_5_MIN.md)
+- [Troubleshooting](docs/TROUBLESHOOTING.md)
+- [Integration guide](docs/INTEGRATION_GUIDE.md)
+- [Publishing](docs/PUBLISHING.md)
+- [Adoption evidence](docs/ADOPTION.md)
+- [Threat model](docs/THREAT_MODEL.md)
+- [Roadmap](ROADMAP.md)
+- [Contributing](CONTRIBUTING.md)
+- [Security](SECURITY.md)
+- [Governance](GOVERNANCE.md)
+- [Support](SUPPORT.md)
+
+## Current public-alpha scope
+
+Included today:
+
+- YAML and JSON claim definitions;
+- bounded argv execution with `shell=False`;
+- deterministic claim hashing;
+- JSON Pointer observations;
+- stdout/stderr/file/JUnit observations;
+- multi-claim suites with aggregate reports;
+- pytest-native quality-gate adapter;
+- digest-pinned hardened Docker execution profile;
+- certificate acceptance policies kept separate from claim verdicts;
+- SHA-256 evidence records;
+- non-secret environment capture;
+- canonical certificate digest;
+- offline certificate verification;
+- certificate comparison;
+- reusable composite GitHub Action;
+- open JSON Schemas;
+- cross-platform CI;
+- adversarial path-boundary tests;
+- general producer-provenance attestation plus a custom ReproCert predicate;
+- privacy-minimized predicate generation;
+- richer JSON output for automation;
+- self-service project scaffolding with `reprocert init`;
+- environment/readiness checks with `reprocert doctor`;
+- generated GitHub Actions workflow on request.
+
+Not included today:
+
+- remote execution;
+- embedded private-key management;
+- OCI publication;
+- distributed benchmark orchestration;
+- general statistical inference;
+- scientific correctness adjudication.
+
+## Verified cross-repository adoption
+
+ReproCert is now consumed by a separate existing AETHER X repository, **AETHER X Governed Intelligence**, without modifying that project's product logic or existing disclosure checker.
+
+The consumer workflow produces and verifies a ReproCert certificate, applies an explicit policy, generates a privacy-minimized predicate, and creates signed GitHub attestations on `main`.
+
+This is a **same-organization cross-repository adoption proof**, not independent third-party adoption.
+
+See [Adoption Evidence](docs/ADOPTION.md).
+
+## Project status
+
+**Public Alpha — v0.2.2 self-service line (`0.2.2a1`)**
+
+ReproCert is suitable for evaluation and contribution. Interfaces may still change before a stable v1.0 release.
+
+## License
+
+Apache License 2.0. See [LICENSE](LICENSE).
+
+---
+
+<p align="center"><strong>AETHER X GLOBAL</strong></p>
+<p align="center">Financial Markets · Artificial Intelligence · Advanced Technology · Research</p>

aetherx_reprocert-0.2.2a1.dist-info/RECORD

@@ -0,0 +1,23 @@
+reprocert/__init__.py,sha256=dWoUxM3yc4rrKk5W4FasCYd_wHwzJGPRpTgFPWfP1gc,51
+reprocert/__main__.py,sha256=k1ocEWawweo1qCJWNFAAvyxz3tcY13dzvCenHszij30,48
+reprocert/attestation.py,sha256=5mCooTGTwe1w5fYJM3ohNYsXYUN_mUaHMOcyTjJFWZc,2245
+reprocert/certificate.py,sha256=U2SRSZQI6y8NFm7FL4XxFCLpXbLPF6PF-1ZbBfEpCPw,909
+reprocert/claim.py,sha256=JPcVn8cAYe0mcIQHxmWZ2x8lujyO_JkdxUZKycgnGHE,6970
+reprocert/cli.py,sha256=F6oOo7iFf4wn96542ipFS1TlyZqYOj6_HcNZEvvw0bg,15586
+reprocert/container.py,sha256=rj32_VONQLM-s0WZ7Wez3rBxcfyBLDtUQzxtveQK1OU,3752
+reprocert/doctor.py,sha256=68NCIg94oXf4rKk301zG7Sfgh9Kn1jZdDQqI_FDBaiQ,5060
+reprocert/environment.py,sha256=B3dF2bK6SU3i_YsLKhuwrzykcn8PiQ_bD6ao2iTE4Sk,2166
+reprocert/init_project.py,sha256=hwP87Qu5PQFkBog1c6UIEtoI3-kBNs8NP6jQ5COViUM,5140
+reprocert/junit.py,sha256=zkZEnaPmNwMPTDcwntRyGVRf5Z1b64kT031GACLp33E,4009
+reprocert/policy.py,sha256=lRG-AtLB1JrhTUG1zK2v9s_yGzxOChsqMYxKQa3Ulcg,7428
+reprocert/pytest_adapter.py,sha256=6Ub_FPofh8MGYG4z79XnxEoQNpQGd9uu2AhS8awGT3M,2443
+reprocert/runner.py,sha256=DRbn1e1Uh5LPWgIT7Us3NK-MW3EnB0yxlknuu34z8dU,9841
+reprocert/suite.py,sha256=giS0UljQpQi66pvILx63W1dW8B3xlHkyGRJGHj4knKc,4914
+reprocert/util.py,sha256=8pGmi__raOJAE0edkvYgIq8D9-fFXwKxb_yIq9T01yw,1420
+reprocert/verification.py,sha256=cZhD7UUVuDoF4IWr0YTx_48wZuviIRg5j2BE1G5HgFU,4663
+aetherx_reprocert-0.2.2a1.dist-info/METADATA,sha256=ZLbjZ6LAPgVXrKenZo4V0y-cKggzyEhCZq3tPFVILAc,13304
+aetherx_reprocert-0.2.2a1.dist-info/WHEEL,sha256=W3fkpkm7-wf9vBI5Z-7s0eWkeM-spu78I8Neb98DeEg,87
+aetherx_reprocert-0.2.2a1.dist-info/entry_points.txt,sha256=Ur0WIcgZSR0Bd4VJg9TulVyZseOUuKfGoBliX0hjVPA,49
+aetherx_reprocert-0.2.2a1.dist-info/licenses/LICENSE,sha256=xx0jnfkXJvxRnG63LTGOxlggYnIysveWIZ6H3PNdCrQ,11357
+aetherx_reprocert-0.2.2a1.dist-info/licenses/NOTICE,sha256=KqAxhBvtlgtZwux1EShXn3nNhThwSesZQmQ8ZgHhq5M,281
+aetherx_reprocert-0.2.2a1.dist-info/RECORD,,

aetherx_reprocert-0.2.2a1.dist-info/WHEEL

@@ -0,0 +1,4 @@
+Wheel-Version: 1.0
+Generator: hatchling 1.32.4
+Root-Is-Purelib: true
+Tag: py3-none-any

aetherx_reprocert-0.2.2a1.dist-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+reprocert = reprocert.cli:main

aetherx_reprocert-0.2.2a1.dist-info/licenses/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 [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.

aetherx_reprocert-0.2.2a1.dist-info/licenses/NOTICE

@@ -0,0 +1,7 @@
+AETHER X ReproCert
+Copyright 2026 AETHER X GLOBAL contributors.
+
+Licensed under the Apache License, Version 2.0.
+
+AETHER X and AETHER X GLOBAL names and associated branding are not licensed
+for trademark use except as required for reasonable attribution and source identification.

reprocert/__init__.py

@@ -0,0 +1,3 @@
+"""AETHER X ReproCert."""
+
+__version__ = "0.2.2a1"

reprocert/__main__.py

@@ -0,0 +1,3 @@
+from .cli import main
+
+raise SystemExit(main())