octp-python 0.2.0__tar.gz

octp_python-0.2.0/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,33 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+---
+name: Bug Report
+about: Something is broken
+labels: type: bug, status: needs-triage
+---
+
+**What happened?**
+
+
+**What did you expect to happen?**
+
+
+**How to reproduce**
+Steps:
+1. 
+2. 
+3. 
+
+**Environment**
+- OS:
+- Python version:
+- octp version:
+
+**Additional context**

octp_python-0.2.0/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,25 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+---
+name: Feature Request  
+about: An idea for improving the tool
+labels: type: tooling, status: needs-triage
+---
+
+**What problem does this solve?**
+Describe the problem, not the solution.
+
+**Who experiences this problem?**
+
+
+**What have you tried instead?**
+
+
+**Additional context**

octp_python-0.2.0/.github/ISSUE_TEMPLATE/spec-question.md

@@ -0,0 +1,26 @@
+---
+name: Spec Question
+about: Describe this issue template's purpose here.
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+---
+name: Spec Question
+about: Something in the specification is unclear or missing
+labels: type: spec, status: needs-triage
+---
+
+**Which section or field?**
+
+
+**What is unclear or missing?**
+
+
+**What do you think it should say, and why?**
+
+
+**Are you willing to submit a PR with a clarification?**
+Yes / No

octp_python-0.2.0/.github/workflows/release.yml

@@ -0,0 +1,34 @@
+name: Release
+
+on:
+  push:
+    tags:
+      - "v*"
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      - name: Install build tools
+        run: pip install build twine
+
+      - name: Build package
+        run: python -m build
+
+      - name: Publish to PyPI
+        env:
+          TWINE_USERNAME: __token__
+          TWINE_PASSWORD: ${{ secrets.PYPI_TOKEN }}
+        run: twine upload dist/*
+
+      - name: Create GitHub Release
+        uses: softprops/action-gh-release@v1
+        with:
+          generate_release_notes: true

octp_python-0.2.0/.github/workflows/test.yml

@@ -0,0 +1,35 @@
+name: Tests
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.11", "3.12"]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install dependencies
+        run: |
+          pip install -e ".[dev]"
+
+      - name: Lint with ruff
+        run: ruff check src/ tests/
+
+      - name: Type check with mypy
+        run: mypy src/
+
+      - name: Run tests
+        run: pytest

octp_python-0.2.0/.gitignore

@@ -0,0 +1,216 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+#poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+#pdm.lock
+#pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+#pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# Abstra
+# Abstra is an AI-powered process automation framework.
+# Ignore directories containing user credentials, local state, and settings.
+# Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#  Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#  that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#  and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#  you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Cursor
+#  Cursor is an AI-powered code editor. `.cursorignore` specifies files/directories to
+#  exclude from AI features like autocomplete and code analysis. Recommended for sensitive data
+#  refer to https://docs.cursor.com/context/ignore-files
+.cursorignore
+.cursorindexingignore
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Deployment tokens and secrets
+pypi-token*
+.twine-token
+.pypi-credentials
+.secrets/
+
+# OCTP generated envelopes (optional - uncomment if you want to commit them)
+# .octp-envelope.json

octp_python-0.2.0/.octp-envelope.json

@@ -0,0 +1,42 @@
+{
+  "octp_version": "0.1",
+  "contribution_id": "91456d79-5179-4f97-bd19-ab4cc0787350",
+  "timestamp": "2026-02-26T13:03:42.609792Z",
+  "repository": "github.com/openoctp/octp-python",
+  "commit_hash": "b453802d6452e8fef317aac922b8a18b8205afa0",
+  "provenance": {
+    "method": "ai_assisted_human_reviewed",
+    "ai_tools": [
+      {
+        "model": "claude-sonnet-4-6",
+        "vendor": "anthropic",
+        "version": "20260226",
+        "usage_type": "architecture_and_implementation"
+      },
+      {
+        "model": "kimi-k2.5",
+        "vendor": "moonshot",
+        "version": "20260226",
+        "usage_type": "implementation_and_scaffolding"
+      }
+    ],
+    "human_review_level": "substantial_modification",
+    "human_review_duration_minutes": null,
+    "developer_id": "email:yussuf.x56@gmail.com"
+  },
+  "verification": {
+    "tests_passed": null,
+    "test_suite_hash": null,
+    "static_analysis": "skipped",
+    "static_analysis_tool": null,
+    "dependency_check": "skipped",
+    "novel_dependencies_introduced": false
+  },
+  "integrity": {
+    "payload_hash": "4138707972978f30b70fe52e01d605479c3d4d053ed103f71722d214aa1ba4f7",
+    "developer_signature": "MEYCIQCzaz3W8R+ciczTU4W+uRY3k2LpZAFRQMe3nE5ebu4jKQIhAID8FpM+sUGw1XOgVt42ABBUi5ajMjJUJSXVW5ByVyoq",
+    "signature_algorithm": "ES256",
+    "signed_at": "2026-02-26T13:03:42.621699Z"
+  },
+  "optional_context": null
+}

octp_python-0.2.0/.octp.toml

@@ -0,0 +1,30 @@
+[policy]
+require_envelope = true
+minimum_review_level = "moderate_review"
+block_on_failed_tests = true
+allow_unreviewed_ai = false
+
+[runners]
+default_profile = "ci"
+test_runner = "pytest"
+linting = "ruff"
+type_checking = "mypy"
+static_analysis = "semgrep"
+security_scan = "bandit"
+dependency_check = "pip-audit"
+secret_detection = "detect-secrets"
+
+[identity]
+require_signed_envelope = true
+key_registry = "github"
+
+# OCTP is built with AI assistance. Every commit declares this honestly.
+# This project eats its own cooking — we use the trust envelope we built.
+[provenance]
+# Default for this repo: AI-assisted with substantial human review
+# Contributors: Update these fields when running `octp sign` interactively
+expected_method = "ai_assisted_human_reviewed"
+ai_tools = [
+    { model = "claude-sonnet-4-6", vendor = "anthropic", usage = "architecture_and_design" },
+    { model = "kimi-k2.5", vendor = "moonshot", usage = "implementation_and_scaffolding" }
+]

octp_python-0.2.0/CHANGELOG.md

@@ -0,0 +1,115 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+Format based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.2.0] — 2026-02-26
+
+### Added
+
+- **Runner Profiles** — Four optimized profiles for different workflows:
+  - `fast`: 3-8 seconds, essential checks only (ruff, bandit, detect-secrets)
+  - `ci`: 30-60 seconds, balanced coverage (pytest, ruff, bandit, pip-audit, detect-secrets)
+  - `security`: 30-60 seconds, security-focused (bandit, pip-audit, detect-secrets, semgrep)
+  - `full`: 2-4 minutes, comprehensive (all 7 runners)
+  - Select via `--profile` flag or `default_profile` in config
+
+- **Parallel Execution** — Runners now execute in parallel using ThreadPoolExecutor
+  - 40-60% faster execution on multi-core machines
+  - Graceful handling of runner crashes
+
+- **New Runners**:
+  - `ruff_runner`: Python linting (Rust-based, very fast)
+  - `mypy_runner`: Type checking for typed codebases
+  - `detect_secrets_runner`: Secret and credential detection
+
+- **Non-Interactive Mode** — Automatic detection of non-TTY environments
+  - Uses sensible defaults (AI-assisted, substantial review)
+  - Shows warning when falling back to defaults
+  - Supports `--yes` flag to suppress warnings
+  - Honest AI disclosure with both Claude and Kimi listed
+
+- **Honest AI Disclosure** — Default provenance for OCTP project:
+  - Method: `ai_assisted_human_reviewed`
+  - AI tools: Claude (Anthropic) and Kimi (Moonshot)
+  - Review level: `substantial_modification`
+  - Demonstrates the tool's own use case
+
+- **Comprehensive Test Suite** — 20 tests covering:
+  - Envelope parsing and validation
+  - Integrity/hashing
+  - Runner profiles and parallel execution
+  - Performance benchmarks
+
+- **Documentation** — Complete documentation suite:
+  - `installation.md`: Platform-specific install guides
+  - `quickstart.md`: 5-minute getting started
+  - `profiles.md`: Detailed profile comparison
+  - `configuration.md`: `.octp.toml` reference
+  - `ci-integration.md`: GitHub Actions, GitLab CI, etc.
+  - `troubleshooting.md`: Common issues and solutions
+
+### Changed
+
+- **Improved Test Display** — Tests now show:
+  - ✓ passed — Tests ran and passed
+  - ✗ failed — Tests ran and failed
+  - ○ skipped — Tests not run (appropriate profile)
+
+- **Better Error Handling** — Graceful degradation:
+  - Handles missing verification tools
+  - Handles network timeouts (pip-audit, safety)
+  - Handles interactive prompt failures
+  - Continues with available tools
+
+- **Code Quality** — Full ruff and mypy compliance
+  - All code passes linting
+  - Type annotations throughout
+  - Clean test fixtures
+
+### Fixed
+
+- **Non-Interactive Crashes** — Tool no longer crashes when prompts fail
+- **Template Text in READMEs** — Removed placeholder text
+- **Runner Base Class** — Fixed abstract method declaration
+- **Import Ordering** — Fixed all ruff I001 errors
+- **Detect-Secrets Exception** — Changed bare except to specific JSONDecodeError
+
+### Removed
+
+- **Safety Runner** — Removed as duplicate of pip-audit
+  - Both check for known CVEs in dependencies
+  - pip-audit is faster and more reliable
+  - Safety remains in codebase but not in profiles
+
+## [0.1.0] — 2026-02-26
+
+### Added
+
+- Initial release of the OCTP reference implementation
+- Core envelope generation with `octp sign`
+- Envelope verification with `octp verify`
+- Repository initialization with `octp init`
+- Pydantic envelope model implementing OCTP spec v0.1
+- ES256 cryptographic signing via the cryptography library
+- Automatic keypair generation and management
+- Git integration via GitPython
+- Verification runners:
+  - pytest_runner: Test execution
+  - semgrep_runner: Static analysis
+  - bandit_runner: Security scanning
+  - deps_runner: Dependency vulnerability check (pip-audit)
+- Rich terminal output with human-readable trust summary
+- `.octp.toml` project configuration
+- JSON Schema for envelope validation
+- Example envelopes (minimal and full)
+- RFC process and governance structure
+- CONTRIBUTING.md and CODE_OF_CONDUCT.md
+
+[Unreleased]: https://github.com/openoctp/octp-python/compare/v0.2.0...HEAD
+[0.2.0]: https://github.com/openoctp/octp-python/compare/v0.1.0...v0.2.0
+[0.1.0]: https://github.com/openoctp/octp-python/releases/tag/v0.1.0

octp_python-0.2.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,85 @@
+
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [INSERT CONTACT METHOD]. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations
+