From 5b57c9b8f08b2936961c993ed10d842cd9e7a5e7 Mon Sep 17 00:00:00 2001 From: "Jonathan D.A. Jewell" <6759885+hyperpolymath@users.noreply.github.com> Date: Sun, 26 Jul 2026 14:44:55 +0100 Subject: [PATCH 1/3] chore: estate-wide security compliance --- .github/workflows/casket-pages.yml | 1 + .github/workflows/codeql.yml | 45 ++++ .github/workflows/governance.yml | 1 + .github/workflows/hypatia-scan.yml | 1 + .github/workflows/mirror.yml | 1 + .github/workflows/pages.yml | 1 + .github/workflows/proof-corpus.yml | 1 + .github/workflows/push-email-notify.yml | 1 + .github/workflows/rust-ci.yml | 1 + .github/workflows/scorecard.yml | 1 + .github/workflows/secret-scanner.yml | 1 + .github/workflows/spark-theatre-gate.yml | 1 + CODE_OF_CONDUCT.md | 327 +++++++++++++++++++++++ 13 files changed, 383 insertions(+) create mode 100644 .github/workflows/codeql.yml create mode 100644 CODE_OF_CONDUCT.md diff --git a/.github/workflows/casket-pages.yml b/.github/workflows/casket-pages.yml index 6b7b42b..dbc2a18 100644 --- a/.github/workflows/casket-pages.yml +++ b/.github/workflows/casket-pages.yml @@ -7,6 +7,7 @@ on: workflow_dispatch: permissions: + actions: read contents: read pages: write id-token: write diff --git a/.github/workflows/codeql.yml b/.github/workflows/codeql.yml new file mode 100644 index 0000000..ae64b5e --- /dev/null +++ b/.github/workflows/codeql.yml @@ -0,0 +1,45 @@ +# SPDX-License-Identifier: MPL-2.0 +name: CodeQL + +on: + push: + branches: [main] + pull_request: + branches: [main] + schedule: + - cron: '0 0 * * 0' + +permissions: + actions: read + contents: read + security-events: write + +jobs: + analyze: + name: CodeQL Analysis + runs-on: ubuntu-latest + permissions: + actions: read + contents: read + security-events: write + strategy: + fail-fast: false + matrix: + include: + - language: actions + build-mode: none + steps: + - name: Checkout repository + uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4 + + - name: Initialize CodeQL + uses: github/codeql-action/init@29b1f65c1f735799893313399435a59f54045865 # v3 + with: + languages: ${{ matrix.language }} + build-mode: ${{ matrix.build-mode }} + + - name: Autobuild + uses: github/codeql-action/autobuild@29b1f65c1f735799893313399435a59f54045865 # v3 + + - name: Perform CodeQL Analysis + uses: github/codeql-action/analyze@29b1f65c1f735799893313399435a59f54045865 # v3 diff --git a/.github/workflows/governance.yml b/.github/workflows/governance.yml index 156264a..cc62f6c 100644 --- a/.github/workflows/governance.yml +++ b/.github/workflows/governance.yml @@ -27,6 +27,7 @@ concurrency: cancel-in-progress: true permissions: + actions: read contents: read jobs: diff --git a/.github/workflows/hypatia-scan.yml b/.github/workflows/hypatia-scan.yml index 2e7e939..013c95a 100644 --- a/.github/workflows/hypatia-scan.yml +++ b/.github/workflows/hypatia-scan.yml @@ -19,6 +19,7 @@ concurrency: cancel-in-progress: true permissions: + actions: read contents: read security-events: write pull-requests: write diff --git a/.github/workflows/mirror.yml b/.github/workflows/mirror.yml index 81e9903..c25d3bc 100644 --- a/.github/workflows/mirror.yml +++ b/.github/workflows/mirror.yml @@ -7,6 +7,7 @@ on: workflow_dispatch: permissions: + actions: read contents: read jobs: diff --git a/.github/workflows/pages.yml b/.github/workflows/pages.yml index 8596374..50092a4 100644 --- a/.github/workflows/pages.yml +++ b/.github/workflows/pages.yml @@ -5,6 +5,7 @@ on: branches: [main, master] workflow_dispatch: permissions: + actions: read contents: read pages: write id-token: write diff --git a/.github/workflows/proof-corpus.yml b/.github/workflows/proof-corpus.yml index 164ead0..e28b75f 100644 --- a/.github/workflows/proof-corpus.yml +++ b/.github/workflows/proof-corpus.yml @@ -18,6 +18,7 @@ on: branches: [main, master] permissions: + actions: read contents: read concurrency: diff --git a/.github/workflows/push-email-notify.yml b/.github/workflows/push-email-notify.yml index 0816771..ce036e2 100644 --- a/.github/workflows/push-email-notify.yml +++ b/.github/workflows/push-email-notify.yml @@ -7,6 +7,7 @@ name: Push email notification on: push: {} permissions: + actions: read contents: read jobs: notify: diff --git a/.github/workflows/rust-ci.yml b/.github/workflows/rust-ci.yml index c4faf69..53ac973 100644 --- a/.github/workflows/rust-ci.yml +++ b/.github/workflows/rust-ci.yml @@ -10,6 +10,7 @@ on: pull_request: permissions: + actions: read contents: read jobs: diff --git a/.github/workflows/scorecard.yml b/.github/workflows/scorecard.yml index e3b925d..145757d 100644 --- a/.github/workflows/scorecard.yml +++ b/.github/workflows/scorecard.yml @@ -15,6 +15,7 @@ on: # `read-all` startup_failure seen estate-wide. Matches the canonical caller in # hyperpolymath/standards/.github/workflows/scorecard-reusable.yml. permissions: + actions: read contents: read jobs: diff --git a/.github/workflows/secret-scanner.yml b/.github/workflows/secret-scanner.yml index b3486fc..4839d60 100644 --- a/.github/workflows/secret-scanner.yml +++ b/.github/workflows/secret-scanner.yml @@ -11,6 +11,7 @@ concurrency: cancel-in-progress: true permissions: + actions: read contents: read jobs: diff --git a/.github/workflows/spark-theatre-gate.yml b/.github/workflows/spark-theatre-gate.yml index a6030a9..651e420 100644 --- a/.github/workflows/spark-theatre-gate.yml +++ b/.github/workflows/spark-theatre-gate.yml @@ -11,6 +11,7 @@ on: branches: [main, master] permissions: + actions: read contents: read jobs: diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 0000000..8267cd4 --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,327 @@ +# Code of Conduct + + + +## Our Pledge + +We as members, contributors, and leaders pledge to make participation in Squisher Corpus 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, colour, 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. + +We recognise that a thriving open source community requires **psychological safety** — an environment where people can contribute, ask questions, make mistakes, and learn without fear of ridicule or retaliation. + +--- + +## Our Standards + +### Expected Behaviour + +The following behaviours contribute to a positive environment: + +**Communication** +- Using welcoming and inclusive language +- Being respectful of differing viewpoints and experiences +- Giving and gracefully accepting constructive feedback +- Assuming good intent while addressing impact +- Communicating clearly and patiently, especially with newcomers + +**Collaboration** +- Focusing on what is best for the community +- Showing empathy and kindness toward other community members +- Being collaborative rather than competitive +- Mentoring and supporting less experienced contributors +- Celebrating others' contributions and successes + +**Professionalism** +- Accepting responsibility and apologising to those affected by our mistakes +- Learning from the experience and avoiding repetition +- Respecting others' time and attention +- Staying on topic in project spaces +- Following project guidelines and conventions + +**Accessibility** +- Using plain language and avoiding unnecessary jargon +- Providing alt text for images and transcripts for audio/video +- Being patient with those using assistive technologies +- Accommodating different communication styles and needs +- Recognising that not everyone communicates the same way + +### Unacceptable Behaviour + +The following behaviours are considered harassment and are unacceptable: + +**Harassment** +- The use of sexualised 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 +- Deliberate intimidation, stalking, or following (online or in-person) +- Unwelcome physical contact or simulated physical contact (e.g., emoji) +- Sustained disruption of talks, events, or online discussions + +**Discrimination** +- Discriminatory jokes and language +- Posting or threatening to post others' personally identifying information ("doxing") +- Advocating for, or encouraging, any of the above behaviour +- Microaggressions — subtle, often unintentional, discriminatory comments or actions + +**Professional Misconduct** +- Publishing others' private information without explicit permission +- Misrepresenting affiliation or contributions +- Plagiarism or claiming credit for others' work +- Retaliating against anyone who reports a Code of Conduct violation +- Other conduct which could reasonably be considered inappropriate in a professional setting + +### Grey Areas + +Some situations require judgement. When uncertain: + +- **Intent vs Impact**: Good intentions do not excuse harmful impact. Focus on making things right. +- **Power Dynamics**: Those with more power (maintainers, employers, experienced contributors) must be especially mindful of their impact. +- **Cultural Differences**: What's acceptable varies by culture. When in doubt, err on the side of caution and ask. +- **Humour**: Jokes at others' expense are rarely funny to everyone. Punch up, not down. + +--- + +## Scope + +This Code of Conduct applies within all community spaces, including: + +**Online Spaces** +- Repository discussions, issues, and pull/merge requests +- Project chat channels (Matrix, Discord, Slack, IRC) +- Mailing lists and forums +- Social media when representing the project +- Video calls and virtual meetings + +**In-Person Spaces** +- Conferences, meetups, and events +- Workshops and training sessions +- Any gathering where you represent the project + +**Representation** +This Code of Conduct also applies when an individual is officially representing the community in public spaces. Examples include: + +- Using an official project email address +- Posting via an official social media account +- Acting as an appointed representative at an event +- Speaking on behalf of the project + +--- + +## Enforcement + +### Reporting + +If you experience or witness unacceptable behaviour, or have any other concerns, please report it as soon as possible. + +**How to Report** + +| Method | Details | Best For | +|--------|---------|----------| +| **Email** | j.d.a.jewell@open.ac.uk | Detailed reports, sensitive matters | +| **Private Message** | Contact any maintainer directly | Quick questions, minor issues | +| **Anonymous Form** | [Link to form if available] | When you need anonymity | + +**What to Include** + +- Your contact information (unless anonymous) +- Names/usernames of those involved +- Description of what happened +- When and where it occurred +- Any witnesses +- Any supporting evidence (screenshots, links) +- How you would like us to respond (if you have a preference) + +**What Happens Next** + +1. You will receive acknowledgment within **48 hours** +2. The maintainers will review the report +3. We may ask for additional information +4. We will determine appropriate action +5. We will inform you of the outcome (respecting others' privacy) + +### Confidentiality + +All reports will be handled with discretion: + +- Reporter identity is protected by default +- Details are shared only with those who need to know +- We will ask before naming you in any communication +- Anonymous reports are accepted and investigated + +### Conflicts of Interest + +If a maintainers member is involved in an incident: + +- They will recuse themselves from the process +- Another maintainer or external party will handle the report +- We will disclose any potential conflicts + +--- + +## Enforcement Guidelines + +The maintainers will follow these guidelines in determining consequences: + +### 1. Correction + +**Community Impact**: Use of inappropriate language or other behaviour deemed unprofessional or unwelcome. + +**Consequence**: A private, written warning providing clarity around the nature of the violation and an explanation of why the behaviour was inappropriate. A public apology may be requested. + +**Duration**: Immediate + +### 2. Warning + +**Community Impact**: A violation through a single incident or series of actions. + +**Consequence**: A warning with consequences for continued behaviour. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period. 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. + +**Duration**: 1-4 weeks + +### 3. Temporary Ban + +**Community Impact**: A serious violation of community standards, including sustained inappropriate behaviour. + +**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period. 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. + +**Duration**: 1-6 months + +### 4. Permanent Ban + +**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behaviour, 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. + +**Duration**: Permanent (with appeal rights after 12 months) + +### Enforcement Across Perimeters + +For contributors with elevated access (Perimeter 2 or 1): + +| Level | Additional Consequence | +|-------|----------------------| +| Correction | Noted in contributor record | +| Warning | Access privileges may be temporarily reduced | +| Temporary Ban | Access reduced to Perimeter 3 for ban duration | +| Permanent Ban | All access revoked | + +--- + +## Appeals + +If you believe an enforcement decision was made in error: + +1. **Wait 7 days** after the decision (cooling-off period) +2. **Email** j.d.a.jewell@open.ac.uk with subject line "Appeal: [Original Report ID]" +3. **Explain** why you believe the decision should be reconsidered +4. **Provide** any new information not previously available + +**Appeals Process** + +- Appeals are reviewed by a different maintainers member than the original +- You will receive a response within 14 days +- The appeals decision is final +- You may only appeal once per incident + +**Grounds for Appeal** + +- Procedural errors in the original investigation +- New evidence not previously available +- Disproportionate response to the violation +- Misunderstanding of facts + +--- + +## Supporting Those Who Report + +We are committed to supporting those who report violations: + +**We Will** +- Believe and take all reports seriously +- Respect your privacy and confidentiality preferences +- Keep you informed of progress (if you wish) +- Take steps to protect you from retaliation +- Provide resources if you need support + +**We Will Not** +- Require you to confront the person directly +- Dismiss reports without investigation +- Reveal your identity without consent +- Tolerate retaliation against reporters +- Rush you to make decisions + +--- + +## Prevention + +Beyond enforcement, we actively work to prevent issues: + +**Onboarding** +- All contributors are expected to read this Code of Conduct +- Perimeter 2 applicants must confirm they've read and understood it +- Maintainers receive additional training on enforcement + +**Culture** +- We model the behaviour we expect +- We intervene early when we see potential issues +- We thank people for positive contributions +- We create opportunities for diverse voices + +**Review** +- This Code of Conduct is reviewed annually +- Community feedback is welcomed +- Changes are communicated clearly + +--- + +## Acknowledgments + +This Code of Conduct is adapted from: + +- [Contributor Covenant](https://www.contributor-covenant.org/), version 2.1 +- [Django Code of Conduct](https://www.djangoproject.com/conduct/) +- [Rust Code of Conduct](https://www.rust-lang.org/policies/code-of-conduct) +- [Python Community Code of Conduct](https://www.python.org/psf/conduct/) + +We thank these communities for their leadership in creating welcoming spaces. + +--- + +## Questions? + +If you have questions about this Code of Conduct: + +- Open a [Discussion](https://github.com/hyperpolymath/squisher-corpus/discussions) (for general questions) +- Email j.d.a.jewell@open.ac.uk (for private questions) +- Contact any maintainer directly + +--- + +## Summary + +**Be kind. Be respectful. Be collaborative.** + +We're all here because we care about this project. Let's make it a place where everyone can do their best work. + +--- + +Last updated: 2026 · Based on Contributor Covenant 2.1 From d13494e057c9637cd6a184ca0785680749f69c04 Mon Sep 17 00:00:00 2001 From: "Jonathan D.A. Jewell" <6759885+hyperpolymath@users.noreply.github.com> Date: Sun, 26 Jul 2026 15:09:10 +0100 Subject: [PATCH 2/3] chore: remove duplicate GOVERNANCE files, keep GOVERNANCE.md --- GOVERNANCE.adoc | 162 ------------------------------------------------ 1 file changed, 162 deletions(-) delete mode 100644 GOVERNANCE.adoc diff --git a/GOVERNANCE.adoc b/GOVERNANCE.adoc deleted file mode 100644 index e41020d..0000000 --- a/GOVERNANCE.adoc +++ /dev/null @@ -1,162 +0,0 @@ -// SPDX-License-Identifier: CC-BY-SA-4.0 -// SPDX-FileCopyrightText: 2026 Jonathan D.A. Jewell -= Governance Model -:toc: preamble - -This document describes the governance model for this repository. - -== Overview - -This repository follows a **Sole Maintainer Governance Model**: - -* Single maintainer (@hyperpolymath) has full authority over the project -* All contributions are welcome and reviewed by the maintainer -* Decisions are made transparently through GitHub issues and discussions -* The project adheres to the hyperpolymath estate policies where applicable - -== Core Principles - -[cols="1,2"] -|=== -| Principle | Description - -| **Benevolent Dictatorship** | Maintainer has final decision authority but seeks community input - -| **Meritocracy** | Contributions are judged on technical merit, not contributor identity - -| **Transparency** | All significant decisions are documented publicly - -| **Consensus-Seeking** | Maintainer prefers consensus but will decide when necessary - -| **Open Contribution** | Anyone can contribute via fork and pull request - -|=== - -== Roles and Permissions - -[cols="1,2,2"] -|=== -| Role | Permissions | Assignment - -| **Maintainer** | Write access, merge rights, admin | @hyperpolymath -| **Contributors** | Read access, fork, submit PRs | All GitHub users -| **Users** | Use the software, report issues | All GitHub users - -|=== - -== Decision Making Framework - -=== Routine Decisions - -* Bug fixes -* Documentation improvements -* Minor feature additions -* Dependency updates - -**Process**: Maintainer reviews and merges PRs that meet quality standards. - -=== Significant Changes - -* New major features -* API changes -* Architecture modifications -* Breaking changes - -**Process**: -. Open issue describing the change -. Discuss with community (minimum 72 hours) -. Maintainer makes final decision -. Document rationale in issue/PR - -=== Structural Decisions - -* Repository purpose/renaming -* License changes -* Ownership transfer -* Deprecation/archival - -**Process**: -. Extended discussion (minimum 1 week) -. Maintainer makes final decision -. Document in CHANGELOG and governance docs - -== Contribution Lifecycle - -[cols="1,2"] -|=== -| Stage | Process - -| **Ideation** | Open issue, discuss feasibility - -| **Development** | Fork, implement, test thoroughly - -| **Review** | Submit PR, maintainer reviews within 7 days - -| **Merge** | Maintainer merges or requests changes - -| **Release** | Maintainer publishes according to project conventions - -|=== - -== Conflict Resolution - -In case of disagreements: - -. Discuss in the relevant GitHub issue or PR -. Provide technical justification for positions -. Maintainer mediates and makes final decision -. Decision is documented and can be revisited later - -== Project Policies - -This repository adheres to hyperpolymath estate-wide policies: - -* **License**: MPL-2.0 for code, CC-BY-SA-4.0 for prose (per standards/LICENCE-POLICY.adoc) -* **Code of Conduct**: Follows hyperpolymath CODE_OF_CONDUCT.md -* **Security**: Follows hyperpolymath SECURITY.md -* **Contributing**: Follows hyperpolymath CONTRIBUTING.adoc conventions - -== Repository-Specific Conventions - -[cols="1,2"] -|=== -| Convention | Description - -| **Signing** | All commits must be signed (SSH or GPG) - -| **SPDX Headers** | All source files must have SPDX license identifiers - -| **Contractiles** | Mustfile, Trustfile, Intendfile, Adjustfile in root - -| **Machine Readable** | META.a2ml in .machine_readable/6a2/ - -| **CI/CD** | GitHub Actions workflows in .github/workflows/ - -|=== - -== Governance Evolution - -As the project grows, this governance model may evolve: - -* **Adding Co-Maintainers**: When contribution volume warrants it -* **Forming a Team**: For complex multi-maintainer projects -* **Adopting TPCF**: For large, multi-repository projects (see rhodium-standard-repositories) - -Changes to this document require the same process as Significant Changes above. - -== See Also - -* link:MAINTAINERS.adoc[Maintainers] -* link:CODE_OF_CONDUCT.md[Code of Conduct] -* link:CONTRIBUTING.adoc[Contributing Guide] -* link:https://github.com/hyperpolymath/standards/blob/main/LICENCE-POLICY.adoc[Estate License Policy] -* link:https://github.com/hyperpolymath/standards[rhodium-standard-repositories (TPCF)] - -== Changelog - -[cols="1,1,1"] -|=== -| Date | Change | By - -| 2026-06-07 | Initial governance model established | @hyperpolymath -|=== From a378b036cdf84c18fb5fdbf97748b20ff320d726 Mon Sep 17 00:00:00 2001 From: "Jonathan D.A. Jewell" <6759885+hyperpolymath@users.noreply.github.com> Date: Mon, 27 Jul 2026 19:06:49 +0100 Subject: [PATCH 3/3] fix(ci): repoint codeql-action at a SHA that exists github/codeql-action@29b1f65c1f735799893313399435a59f54045865 is pinned here but exists in no repository -- the GitHub API returns 422 for it. CodeQL therefore could not start: the run graph fails to build and the job reports startup_failure, so this repository has had no CodeQL scanning at all. Repointed at 4187e74d05793876e9989daffde9c3e66b4acd07, which is what the v3 tag currently resolves to (v3.37.3), verified against the API. Found while auditing the estate: the same non-existent SHA is pinned in over 100 repositories, so CodeQL is dead across nearly all of them. Co-Authored-By: Claude Opus 5 Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com> --- .github/workflows/codeql.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/workflows/codeql.yml b/.github/workflows/codeql.yml index ae64b5e..34ae58e 100644 --- a/.github/workflows/codeql.yml +++ b/.github/workflows/codeql.yml @@ -33,13 +33,13 @@ jobs: uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4 - name: Initialize CodeQL - uses: github/codeql-action/init@29b1f65c1f735799893313399435a59f54045865 # v3 + uses: github/codeql-action/init@4187e74d05793876e9989daffde9c3e66b4acd07 # v3 with: languages: ${{ matrix.language }} build-mode: ${{ matrix.build-mode }} - name: Autobuild - uses: github/codeql-action/autobuild@29b1f65c1f735799893313399435a59f54045865 # v3 + uses: github/codeql-action/autobuild@4187e74d05793876e9989daffde9c3e66b4acd07 # v3 - name: Perform CodeQL Analysis - uses: github/codeql-action/analyze@29b1f65c1f735799893313399435a59f54045865 # v3 + uses: github/codeql-action/analyze@4187e74d05793876e9989daffde9c3e66b4acd07 # v3