Merge branch 'main' into claude/polysafe-gitfixer-01EqWNatioYDiE4ATbYBBbgr

hyperpolymath · web-flow · commit 24d0ea60537e · 2025-12-07T16:10:45.000+01:00
Signed-off-by: Jonathan D.A. Jewell &lt;6759885+hyperpolymath@users.noreply.github.com&gt;
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.
diff --git a/.github/ISSUE_TEMPLATE/custom.md b/.github/ISSUE_TEMPLATE/custom.md
@@ -0,0 +1,10 @@
+---
+name: Custom issue template
+about: Describe this issue template's purpose here.
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.
diff --git a/.github/dependabot.yml b/.github/dependabot.yml
@@ -0,0 +1,11 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
+
+version: 2
+updates:
+  - package-ecosystem: "" # See documentation for possible values
+    directory: "/" # Location of package manifests
+    schedule:
+      interval: "daily"
diff --git a/.github/workflows/codeql.yml b/.github/workflows/codeql.yml
@@ -0,0 +1,101 @@
+# For most projects, this workflow file will not need changing; you simply need
+# to commit it to your repository.
+#
+# You may wish to alter this file to override the set of languages analyzed,
+# or to provide custom queries or build logic.
+#
+# ******** NOTE ********
+# We have attempted to detect the languages in your repository. Please check
+# the `language` matrix defined below to confirm you have the correct set of
+# supported CodeQL languages.
+#
+name: "CodeQL Advanced"
+
+on:
+  push:
+    branches: [ "main" ]
+  pull_request:
+    branches: [ "main" ]
+  schedule:
+    - cron: '15 14 * * 3'
+
+jobs:
+  analyze:
+    name: Analyze (${{ matrix.language }})
+    # Runner size impacts CodeQL analysis time. To learn more, please see:
+    #   - https://gh.io/recommended-hardware-resources-for-running-codeql
+    #   - https://gh.io/supported-runners-and-hardware-resources
+    #   - https://gh.io/using-larger-runners (GitHub.com only)
+    # Consider using larger runners or machines with greater resources for possible analysis time improvements.
+    runs-on: ${{ (matrix.language == 'swift' && 'macos-latest') || 'ubuntu-latest' }}
+    permissions:
+      # required for all workflows
+      security-events: write
+
+      # required to fetch internal or private CodeQL packs
+      packages: read
+
+      # only required for workflows in private repositories
+      actions: read
+      contents: read
+
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+        - language: actions
+          build-mode: none
+        - language: rust
+          build-mode: none
+        # CodeQL supports the following values keywords for 'language': 'actions', 'c-cpp', 'csharp', 'go', 'java-kotlin', 'javascript-typescript', 'python', 'ruby', 'rust', 'swift'
+        # Use `c-cpp` to analyze code written in C, C++ or both
+        # Use 'java-kotlin' to analyze code written in Java, Kotlin or both
+        # Use 'javascript-typescript' to analyze code written in JavaScript, TypeScript or both
+        # To learn more about changing the languages that are analyzed or customizing the build mode for your analysis,
+        # see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning.
+        # If you are analyzing a compiled language, you can modify the 'build-mode' for that language to customize how
+        # your codebase is analyzed, see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v4
+
+    # Add any setup steps before running the `github/codeql-action/init` action.
+    # This includes steps like installing compilers or runtimes (`actions/setup-node`
+    # or others). This is typically only required for manual builds.
+    # - name: Setup runtime (example)
+    #   uses: actions/setup-example@v1
+
+    # Initializes the CodeQL tools for scanning.
+    - name: Initialize CodeQL
+      uses: github/codeql-action/init@v4
+      with:
+        languages: ${{ matrix.language }}
+        build-mode: ${{ matrix.build-mode }}
+        # If you wish to specify custom queries, you can do so here or in a config file.
+        # By default, queries listed here will override any specified in a config file.
+        # Prefix the list here with "+" to use these queries and those in the config file.
+
+        # For more details on CodeQL's query packs, refer to: https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs
+        # queries: security-extended,security-and-quality
+
+    # If the analyze step fails for one of the languages you are analyzing with
+    # "We were unable to automatically build your code", modify the matrix above
+    # to set the build mode to "manual" for that language. Then modify this step
+    # to build your code.
+    # ℹ️ Command-line programs to run using the OS shell.
+    # 📚 See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun
+    - name: Run manual build steps
+      if: matrix.build-mode == 'manual'
+      shell: bash
+      run: |
+        echo 'If you are using a "manual" build mode for one or more of the' \
+          'languages you are analyzing, replace this with the commands to build' \
+          'your code, for example:'
+        echo '  make bootstrap'
+        echo '  make release'
+        exit 1
+
+    - name: Perform CodeQL Analysis
+      uses: github/codeql-action/analyze@v4
+      with:
+        category: "/language:${{matrix.language}}"
diff --git a/.github/workflows/jekyll-gh-pages.yml b/.github/workflows/jekyll-gh-pages.yml
@@ -0,0 +1,51 @@
+# Sample workflow for building and deploying a Jekyll site to GitHub Pages
+name: Deploy Jekyll with GitHub Pages dependencies preinstalled
+
+on:
+  # Runs on pushes targeting the default branch
+  push:
+    branches: ["main"]
+
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
+# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
+concurrency:
+  group: "pages"
+  cancel-in-progress: false
+
+jobs:
+  # Build job
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+      - name: Setup Pages
+        uses: actions/configure-pages@v5
+      - name: Build with Jekyll
+        uses: actions/jekyll-build-pages@v1
+        with:
+          source: ./
+          destination: ./_site
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3
+
+  # Deployment job
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    needs: build
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4
diff --git a/.gitignore b/.gitignore
@@ -5,7 +5,7 @@
 # Rust
 # ==============================================================================
 target/
-# Note: Cargo.lock IS tracked for reproducible Nix builds
+Cargo.lock
 **/*.rs.bk
 *.pdb
 
@@ -68,11 +68,6 @@ result
 result-*
 .direnv/
 
-# Local Nix shell directories (created by shellHook)
-.nix-mix/
-.nix-hex/
-.cabal/
-
 # ==============================================================================
 # Editor/IDE
 # ==============================================================================
diff --git a/SECURITY.md b/SECURITY.md
@@ -2,118 +2,20 @@
 
 ## Supported Versions
 
+Use this section to tell people about which versions of your project are
+currently being supported with security updates.
+
 | Version | Supported          |
 | ------- | ------------------ |
-| 0.1.x   | :white_check_mark: |
+| 5.1.x   | :white_check_mark: |
+| 5.0.x   | :x:                |
+| 4.0.x   | :white_check_mark: |
+| < 4.0   | :x:                |
 
 ## Reporting a Vulnerability
 
-We take security vulnerabilities seriously. If you discover a security issue,
-please report it responsibly.
-
-### How to Report
-
-1. **Preferred Method**: Open a confidential security issue on GitLab
-   - Go to Issues → New Issue → Check "This issue is confidential"
-
-2. **Email**: Send details to the maintainers listed in MAINTAINERS.md
-   - Include "SECURITY" in the subject line
-   - Use PGP encryption if available
-
-3. **Do NOT**:
-   - Open public issues for security vulnerabilities
-   - Disclose the vulnerability publicly before it's fixed
-   - Exploit the vulnerability beyond proof-of-concept
-
-### What to Include
-
-- Description of the vulnerability
-- Steps to reproduce
-- Potential impact assessment
-- Suggested fix (if any)
-- Your contact information for follow-up
-
-### Response Timeline
-
-| Severity | Acknowledgment | Target Resolution |
-|----------|----------------|-------------------|
-| Critical | 4 hours        | 24 hours          |
-| High     | 12 hours       | 72 hours          |
-| Medium   | 24 hours       | 1 week            |
-| Low      | 48 hours       | 1 month           |
-
-### Severity Classification
-
-- **Critical**: Remote code execution, data corruption, privilege escalation
-- **High**: Path traversal, audit log tampering, authentication bypass
-- **Medium**: Information disclosure, denial of service
-- **Low**: Minor information leaks, documentation issues
-
-## Security Design
-
-polysafe-gitfixer is designed with security as a primary concern:
-
-### Type-Safe Languages
-
-All core components use memory-safe, type-safe languages:
-- **Rust**: Memory safety without garbage collection
-- **Haskell**: Strong static typing, totality checking
-- **Elixir/OTP**: Process isolation, fault tolerance
-- **Idris**: Dependent types for correctness proofs
-
-### Capability-Based Security
-
-The `capability` crate implements:
-- **Path Traversal Prevention**: All filesystem access goes through `DirCapability`
-- **Unforgeable Tokens**: Capabilities cannot be forged or escalated
-- **Principle of Least Privilege**: Capabilities grant minimum required access
-
-### Audit Logging
-
-- **Hash-Chained Log**: Each entry includes SHA-256 hash of previous entry
-- **Tamper Evidence**: Any modification breaks the chain
-- **Append-Only**: Log entries cannot be modified or deleted
-
-### Transactional Operations
-
-- **RAII Cleanup**: Resources freed automatically on scope exit
-- **Atomic Operations**: Write-to-temp, then rename
-- **Rollback on Failure**: Incomplete operations are automatically reversed
-
-## Security Practices
-
-### Development
-
-- All code requires review before merge
-- Automated security scanning in CI/CD
-- Dependency vulnerability monitoring
-- SPDX license headers on all source files
-
-### Testing
-
-- Unit tests for security-critical functions
-- Property-based testing for edge cases
-- Integration tests for capability boundaries
-
-### Dependencies
-
-We minimize dependencies and prefer:
-- Well-audited, widely-used libraries
-- Libraries with security-focused maintainers
-- Pure Rust implementations over C bindings where practical
-
-## Acknowledgments
-
-We maintain a security acknowledgments list for responsible disclosures.
-Reporters may choose to be credited publicly or remain anonymous.
-
-## Contact
-
-For security questions that don't involve vulnerabilities, you may:
-- Open a regular issue with the "security-question" label
-- Ask in project discussions
-
----
+Use this section to tell people how to report a vulnerability.
 
-This security policy follows [RFC 9116](https://www.rfc-editor.org/rfc/rfc9116) guidelines.
-See `.well-known/security.txt` for machine-readable security contact information.
+Tell them where to go, how often they can expect to get an update on a
+reported vulnerability, what to expect if the vulnerability is accepted or
+declined, etc.
