oept 0.1.1__tar.gz

oept-0.1.1/LICENSE

@@ -0,0 +1,200 @@
+                                 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 don't recommend using
+      this address for actual confirmation of the license; it is given
+      here as a convenience.
+
+   Copyright 2026 OEPT Contributors
+
+   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.

oept-0.1.1/MANIFEST.in

@@ -0,0 +1,8 @@
+graft schemas
+graft spec
+graft examples
+graft conformance
+graft docs
+global-exclude __pycache__
+global-exclude *.py[cod]
+global-exclude .DS_Store

oept-0.1.1/PKG-INFO

@@ -0,0 +1,147 @@
+Metadata-Version: 2.4
+Name: oept
+Version: 0.1.1
+Summary: Open Evidence Provenance Toolkit: content-addressed evidence objects, portable signed bundles, offline verification
+Author: OEPT Contributors
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/fintegra-ai/open-evidence-provenance
+Project-URL: Repository, https://github.com/fintegra-ai/open-evidence-provenance
+Keywords: provenance,supply-chain,integrity,verification,evidence
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+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: Topic :: Security
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: cryptography>=41
+Requires-Dist: jcs>=0.2
+Requires-Dist: jsonschema>=4.18
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == "dev"
+Requires-Dist: ruff>=0.4; extra == "dev"
+Requires-Dist: mypy>=1.8; extra == "dev"
+Provides-Extra: test
+Requires-Dist: pytest>=8; extra == "test"
+Dynamic: license-file
+
+# Open Evidence Provenance Toolkit (OEPT)
+
+Small, dependency-light infrastructure for **evidence provenance**:
+prove *which exact source version produced which claim*, and let any
+third party verify the package **offline** — without trusting your servers.
+
+```
+source bytes → content digest → provenance metadata → portable bundle → offline verification
+```
+
+## The problem
+
+Software and data pipelines transform source files through parsing,
+normalization, mappings, validation, and deterministic controls. Downstream
+users — auditors, integrators, regulators, customers — frequently cannot
+independently determine which source object produced a claim, which exact
+version was used, which transformation ran, when it was observed, whether
+the source changed later, or whether an exported package was modified.
+
+OEPT provides reusable primitives for that chain:
+content-addressed evidence objects, append-only observation history,
+deterministic canonicalization, portable signed bundles, and an offline
+verifier. The project emerged from work on evidence-intensive systems
+including financial and regulatory workflows, but OEPT itself is
+domain-neutral: it works with arbitrary data files.
+
+## Trust boundary (read first)
+
+OEPT proves: bundle structure, member presence, SHA-256 integrity,
+manifest integrity, safe archive structure, Ed25519 signature validity,
+supplied trusted-key identity.
+
+OEPT never claims: factual truth, commercial truth, legal validity,
+compliance approval, fraud detection, eIDAS qualification, timestamps,
+certificate chains, or malware-free status.
+
+## Quickstart
+
+```bash
+pip install -e .
+oept verify examples/valid-unsigned.zip
+```
+
+Expected output:
+
+```
+Bundle: examples/valid-unsigned.zip
+Specification: oept-bundle/0.1
+Structure: VALID
+Member digests: VALID
+Signature: NOT PRESENT
+Result: VALID_UNSIGNED
+
+Technical verification only — not a legal, compliance, or factual conclusion.
+```
+
+Build a bundle from a prepared directory (containing `facts.json`,
+`provenance.json`, and `evidence/`):
+
+```bash
+oept bundle examples/evidence-project --output my-evidence.zip
+oept verify my-evidence.zip --json
+```
+
+Signed bundles:
+
+```bash
+oept bundle DIR --output signed.zip --sign my-key.pem --key-id ops-2026
+oept verify signed.zip --trust-keys trust-keys.json
+```
+
+Trust roots always come from `--trust-keys`. Keys embedded in a bundle
+are identification labels only and are never trusted automatically.
+
+## Bundle anatomy (oept-bundle/0.1)
+
+Required: `manifest.json`, `facts.json`, `provenance.json`, `evidence/`.
+Optional: `metadata/`, `rule_traces.json`, `signatures/manifest.sig`,
+`signatures/key-info.json`, `SUMMARY.txt`.
+Full rules: `spec/bundle-spec.md`.
+
+Verification statuses: `VALID_SIGNED`, `VALID_UNSIGNED`, `HASH_MISMATCH`,
+`MISSING_FILE`, `UNEXPECTED_FILE`, `SIGNATURE_INVALID`,
+`SIGNATURE_KEY_UNKNOWN`, `UNSUPPORTED_SPEC_VERSION`, `UNSAFE_ARCHIVE`,
+`MALFORMED_BUNDLE`.
+
+## Relationship to existing standards
+
+OEPT complements rather than replaces: in-toto, SLSA, Sigstore, W3C PROV,
+RO-Crate, SCITT, SPDX, CycloneDX. None of these today gives field-level
+source-bytes→claim lineage in one stdlib-friendly offline bundle without
+a daemon, OIDC, RDF store, or log operator — that narrow gap is OEPT's
+reason to exist. Interoperability adapters (in-toto statement emission,
+PROV export) are planned grant work; v0.1 claims no compatibility beyond
+its own spec. See `docs/roadmap.md`.
+
+## Roadmap
+
+- v0.1 (this release): schemas, SDK core (canonical/hash/bundle/verify),
+  CLI, conformance corpus, specs.
+- Grant work (planned): EvidenceStore (SQLite), source-mapping profiles,
+  rule-trace emitter, snapshot pinning, W3C PROV + in-toto exporters,
+  transparency-log anchoring study.
+
+## Security reporting
+
+See SECURITY.md. Until a dedicated project security address is published,
+report privately through the repository hosting platform's security
+advisory mechanism.
+
+## License
+
+Apache-2.0. See LICENSE.

oept-0.1.1/README.md

@@ -0,0 +1,113 @@
+# Open Evidence Provenance Toolkit (OEPT)
+
+Small, dependency-light infrastructure for **evidence provenance**:
+prove *which exact source version produced which claim*, and let any
+third party verify the package **offline** — without trusting your servers.
+
+```
+source bytes → content digest → provenance metadata → portable bundle → offline verification
+```
+
+## The problem
+
+Software and data pipelines transform source files through parsing,
+normalization, mappings, validation, and deterministic controls. Downstream
+users — auditors, integrators, regulators, customers — frequently cannot
+independently determine which source object produced a claim, which exact
+version was used, which transformation ran, when it was observed, whether
+the source changed later, or whether an exported package was modified.
+
+OEPT provides reusable primitives for that chain:
+content-addressed evidence objects, append-only observation history,
+deterministic canonicalization, portable signed bundles, and an offline
+verifier. The project emerged from work on evidence-intensive systems
+including financial and regulatory workflows, but OEPT itself is
+domain-neutral: it works with arbitrary data files.
+
+## Trust boundary (read first)
+
+OEPT proves: bundle structure, member presence, SHA-256 integrity,
+manifest integrity, safe archive structure, Ed25519 signature validity,
+supplied trusted-key identity.
+
+OEPT never claims: factual truth, commercial truth, legal validity,
+compliance approval, fraud detection, eIDAS qualification, timestamps,
+certificate chains, or malware-free status.
+
+## Quickstart
+
+```bash
+pip install -e .
+oept verify examples/valid-unsigned.zip
+```
+
+Expected output:
+
+```
+Bundle: examples/valid-unsigned.zip
+Specification: oept-bundle/0.1
+Structure: VALID
+Member digests: VALID
+Signature: NOT PRESENT
+Result: VALID_UNSIGNED
+
+Technical verification only — not a legal, compliance, or factual conclusion.
+```
+
+Build a bundle from a prepared directory (containing `facts.json`,
+`provenance.json`, and `evidence/`):
+
+```bash
+oept bundle examples/evidence-project --output my-evidence.zip
+oept verify my-evidence.zip --json
+```
+
+Signed bundles:
+
+```bash
+oept bundle DIR --output signed.zip --sign my-key.pem --key-id ops-2026
+oept verify signed.zip --trust-keys trust-keys.json
+```
+
+Trust roots always come from `--trust-keys`. Keys embedded in a bundle
+are identification labels only and are never trusted automatically.
+
+## Bundle anatomy (oept-bundle/0.1)
+
+Required: `manifest.json`, `facts.json`, `provenance.json`, `evidence/`.
+Optional: `metadata/`, `rule_traces.json`, `signatures/manifest.sig`,
+`signatures/key-info.json`, `SUMMARY.txt`.
+Full rules: `spec/bundle-spec.md`.
+
+Verification statuses: `VALID_SIGNED`, `VALID_UNSIGNED`, `HASH_MISMATCH`,
+`MISSING_FILE`, `UNEXPECTED_FILE`, `SIGNATURE_INVALID`,
+`SIGNATURE_KEY_UNKNOWN`, `UNSUPPORTED_SPEC_VERSION`, `UNSAFE_ARCHIVE`,
+`MALFORMED_BUNDLE`.
+
+## Relationship to existing standards
+
+OEPT complements rather than replaces: in-toto, SLSA, Sigstore, W3C PROV,
+RO-Crate, SCITT, SPDX, CycloneDX. None of these today gives field-level
+source-bytes→claim lineage in one stdlib-friendly offline bundle without
+a daemon, OIDC, RDF store, or log operator — that narrow gap is OEPT's
+reason to exist. Interoperability adapters (in-toto statement emission,
+PROV export) are planned grant work; v0.1 claims no compatibility beyond
+its own spec. See `docs/roadmap.md`.
+
+## Roadmap
+
+- v0.1 (this release): schemas, SDK core (canonical/hash/bundle/verify),
+  CLI, conformance corpus, specs.
+- Grant work (planned): EvidenceStore (SQLite), source-mapping profiles,
+  rule-trace emitter, snapshot pinning, W3C PROV + in-toto exporters,
+  transparency-log anchoring study.
+
+## Security reporting
+
+See SECURITY.md. Until a dedicated project security address is published,
+report privately through the repository hosting platform's security
+advisory mechanism.
+
+## License
+
+Apache-2.0. See LICENSE.

oept-0.1.1/conformance/fixtures/01-valid-unsigned/expected-result.json

@@ -0,0 +1,3 @@
+{
+  "status": "VALID_UNSIGNED"
+}

oept-0.1.1/conformance/fixtures/02-valid-signed/expected-result.json

@@ -0,0 +1,3 @@
+{
+  "status": "VALID_SIGNED"
+}

oept-0.1.1/conformance/fixtures/02-valid-signed/trust-keys.json

@@ -0,0 +1,6 @@
+[
+  {
+    "key_id": "conformance-test-key",
+    "public_key_pem": "-----BEGIN PUBLIC KEY-----\nMCowBQYDK2VwAyEAZHQFbcEU4SxGXn6EY0Xz6By9k70sQUa2DxU+mqfPgFc=\n-----END PUBLIC KEY-----\n"
+  }
+]

oept-0.1.1/conformance/fixtures/03-tampered-artifact/expected-result.json

@@ -0,0 +1,3 @@
+{
+  "status": "HASH_MISMATCH"
+}

oept-0.1.1/conformance/fixtures/04-missing-member/expected-result.json

@@ -0,0 +1,3 @@
+{
+  "status": "MISSING_FILE"
+}

oept-0.1.1/conformance/fixtures/05-unsafe-path/expected-result.json

@@ -0,0 +1,3 @@
+{
+  "status": "UNSAFE_ARCHIVE"
+}

oept-0.1.1/conformance/fixtures/06-signature-invalid/expected-result.json

@@ -0,0 +1,3 @@
+{
+  "status": "SIGNATURE_INVALID"
+}

oept-0.1.1/conformance/fixtures/06-signature-invalid/trust-keys.json

@@ -0,0 +1,6 @@
+[
+  {
+    "key_id": "conformance-test-key",
+    "public_key_pem": "-----BEGIN PUBLIC KEY-----\nMCowBQYDK2VwAyEAZHQFbcEU4SxGXn6EY0Xz6By9k70sQUa2DxU+mqfPgFc=\n-----END PUBLIC KEY-----\n"
+  }
+]

oept-0.1.1/conformance/fixtures/07-unknown-key/expected-result.json

@@ -0,0 +1,3 @@
+{
+  "status": "SIGNATURE_KEY_UNKNOWN"
+}

oept-0.1.1/conformance/fixtures/08-unexpected-member/expected-result.json

@@ -0,0 +1,3 @@
+{
+  "status": "UNEXPECTED_FILE"
+}

oept-0.1.1/conformance/fixtures/09-unsupported-version/expected-result.json

@@ -0,0 +1,3 @@
+{
+  "status": "UNSUPPORTED_SPEC_VERSION"
+}

oept-0.1.1/conformance/fixtures/10-malformed-manifest/expected-result.json

@@ -0,0 +1,3 @@
+{
+  "status": "MALFORMED_BUNDLE"
+}