challenge-toolkit 1.2.0rc2__tar.gz

challenge_toolkit-1.2.0rc2/.github/CODEOWNERS

@@ -0,0 +1,2 @@
+# Require review from security/maintainers for workflows
+.github/** @ctfpilot/devops

challenge_toolkit-1.2.0rc2/.github/workflows/ci.yaml

@@ -0,0 +1,49 @@
+name: CI
+
+on:
+  push:
+    branches:
+      - main
+      - develop
+  pull_request:
+    branches:
+      - main
+      - develop
+
+jobs:
+  build:
+    name: Build and Test
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+
+    strategy:
+      matrix:
+        python-version: ["3.10", "3.11", "3.12", "3.13", "3.14"]
+      fail-fast: false
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@803947b9bd8e9f986429fa0c5a41c367cd732b41 # v7
+        with:
+          enable-cache: true
+
+      - name: Set up Python
+        uses: actions/setup-python@a309ff8b426b58ec0e2a45f0f869d46889d02405 # v6
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install the project
+        run: uv sync --locked --all-extras --dev
+
+      - name: Build project
+        run: uv build
+
+      - name: Run tests
+        run: uv run pytest
+
+      - name: Minimize uv cache
+        run: uv cache prune --ci

challenge_toolkit-1.2.0rc2/.github/workflows/cla-assistant.yml

@@ -0,0 +1,20 @@
+name: "CLA Assistant"
+on:
+  issue_comment:
+    types: [created]
+  pull_request_target:
+    types: [opened, closed, synchronize]
+
+permissions:
+  actions: write
+  contents: read
+  pull-requests: write
+  statuses: write
+
+jobs:
+  CLAAssistant:
+    name: "CLA Assistant"
+    uses: ctfpilot/ci/.github/workflows/cla-assistant.yml@v1.3.0
+    secrets: inherit
+    with:
+      repository: challenge-toolkit

challenge_toolkit-1.2.0rc2/.github/workflows/release.yml

@@ -0,0 +1,23 @@
+name: Release
+
+on:
+  push:
+    branches:
+      - main
+      - develop
+
+jobs:
+  release:
+    name: Release
+    uses: ctfpilot/ci/.github/workflows/release.yml@v1.4.0
+    permissions:
+      contents: write
+      packages: write
+      id-token: write
+    secrets:
+      RELEASE_GH_TOKEN: ${{ secrets.RELEASE_GH_TOKEN }}
+      PYPI_TOKEN: ${{ secrets.PYPI_TOKEN }}
+    with:
+      repository: ctfpilot/challenge-toolkit
+      plugins: "semantic-release-pypi"
+      ENVIRONMENT: Release

challenge_toolkit-1.2.0rc2/.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
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# 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
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml

challenge_toolkit-1.2.0rc2/.releaserc.json

@@ -0,0 +1,51 @@
+{
+    "branches": [
+        "main",
+        {
+            "name": "develop",
+            "prerelease": "rc"
+        }
+    ],
+    "plugins": [
+        [
+            "@semantic-release/commit-analyzer",
+            {
+                "preset": "conventionalcommits"
+            }
+        ],
+        [
+            "@semantic-release/release-notes-generator",
+            {
+                "preset": "conventionalcommits"
+            }
+        ],
+        [
+            "@semantic-release/exec",
+            {
+                "prepareCmd": "echo ${nextRelease.version} > version.txt",
+                "publishCmd": "echo 'Published version ${nextRelease.version}'"
+            }
+        ],
+        [
+            "semantic-release-pypi",
+            {
+                "pypiPublish": true
+            }
+        ],
+        [
+            "@semantic-release/git",
+            {
+                "assets": [
+                    "pyproject.toml"
+                ],
+                "message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
+            }
+        ],
+        [
+            "@semantic-release/github",
+            {
+                "successComment": false
+            }
+        ]
+    ]
+}

challenge_toolkit-1.2.0rc2/CLA.md

@@ -0,0 +1,5 @@
+# indieopensource.com Tiny Contributor License Agreement 1.0.0
+
+I, {{{contributor name}}}, give CTF Pilot permission to license my contributions on any terms they like.  I am giving them this license in order to make it possible for them to accept my contributions into their project.
+
+***As far as the law allows, my contributions come as is, without any warranty or condition, and I will not be liable to anyone for any damages related to this software or this license, under any kind of legal claim.***

challenge_toolkit-1.2.0rc2/CODEOWNERS

@@ -0,0 +1,2 @@
+# Require review from security/maintainers for workflows
+.releaserc.json @ctfpilot/devops

challenge_toolkit-1.2.0rc2/CODE_OF_CONDUCT.md

@@ -0,0 +1,43 @@
+# Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+- Using welcoming and inclusive language
+- Respecting differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned with this Code of Conduct, or to ban temporarily or permanently any contributor for behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project email 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 by contacting the project team. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain the confidentiality of the reporter of any incident.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), version 2.0, available at <https://www.contributor-covenant.org/version/2/0/code_of_conduct.html>

challenge_toolkit-1.2.0rc2/CONTRIBUTING.md

@@ -0,0 +1,99 @@
+# Contributing to CTF Pilot
+
+Thank you for considering contributing to CTF Pilot!  
+We appreciate your interest in helping us enhance our platform and tools.
+
+## Contribution Guidelines
+
+We welcome contributions from the community to enhance CTF Pilot.  
+To ensure a smooth and efficient contribution process, please adhere to the following guidelines:
+
+### Reporting Issues
+
+If you encounter a bug, have a suggestion, or wish to discuss improvements, please open an issue in the repository That is appropriate for the bug.  
+When reporting issues, provide detailed information, steps to reproduce, and, if possible, screenshots or logs to help us understand and resolve the problem efficiently.
+
+### Code Contributions
+
+1. **Fork the Repository:** Fork the CTF Pilot repository you want to contribute code to, to your GitHub account.
+2. **Branching:** Create a new branch from the `develop` branch for your changes. Use descriptive branch names that reflect the changes made. If you are working on an issue, reference the issue number in your branch name (e.g., `feature/123`). See the [Branch Naming](#branch-naming) section for more information.
+3. **Commit Guidelines:** Follow our [Versioning Guidelines](#versioning-guidelines) to use commit messages that bump the versioning. We recommend also doing this in squash commits.  
+For general commits, follow descriptive commit messages that succinctly describe the changes made.  
+Reference any related issues or pull requests in your commits using appropriate keywords (e.g., "Fix #123").
+4. **Code Style:** Maintain consistent code style and formatting as per the existing project standards.
+5. **Testing:** Ensure new code is accompanied by relevant tests where applicable.
+6. **Pull Requests:** Submit a pull request against the `develop` branch. Provide a clear description of your changes, ensuring it aligns with the outlined issue or feature request.
+7. **Accept CLA:** If prompted, please accept the Contributor License Agreement (CLA) to formalize your contribution. Read more about the CLA in the [CLA repository](https://github.com/ctfpilot/cla).  
+We require all contributors to sign the CLA to ensure that contributions can be legally incorporated into the project.
+8. **Review Process:** Be responsive to feedback during the review process. Address any requested changes to facilitate the merging of your contribution.
+9. **Merging:** Once approved, your changes will be merged into the `develop` branch and subsequently into the `main` branch for release.
+Code merging is done at the discretion of the maintainers. They hold the full right to accept or reject any contributions.
+
+### Versioning Guidelines
+
+CTF Pilot adheres to [semantic versioning](https://semver.org/) principles:
+
+- **MAJOR version** for incompatible changes,
+- **MINOR version** for backward-compatible functionality additions, and
+- **PATCH version** for backward-compatible bug fixes.
+
+### Automatic Versioning with semantic-release
+
+CTF Pilot uses [semantic-release](https://github.com/semantic-release/semantic-release) for versioning and releases. Upon merging changes into the `main` branch, semantic-release generates new versions and publishes them. Merges to `develop` creates pre-releases.
+
+Commit messages follow this format for automated versioning: `<type>(<category>): <message>`
+
+#### Commit Types
+
+Commit types are:
+
+- `fix` - For bug fixes or minor changes. Bumps the PATCH version.
+- `feat` - For new features. Bumps the MINOR version.
+- `perf` - Major breaking changes. Bumps the MAJOR version.
+
+*These are the main types, but there are others, such as `chore`, `docs`, `test`, etc. These will not trigger a version bump.*
+*For more information, see [semantic-release](https://github.com/semantic-release/semantic-release).*
+
+***Types are case-sensitive.***
+
+#### Categories
+
+For categories, we don't have a full list, but this is a core list, of example categories:
+
+- `core` - For core changes.
+- `format` - For format changes.
+- `docs` - For documentation changes.
+- `misc` - For miscellaneous changes.
+- `infra` - For infrastructure changes.
+
+We suggest, trying to use a category that will fit, but if you can't find one, you can use `misc` or completely omit it (e.g., `feat: message`).
+
+### Branch naming
+
+When developing, we try to follow some guidelines for branch naming, when possible.
+
+The main branches are:
+
+- `main` - For stable releases.
+- `develop` - For pre-releases.
+
+For other branches, try the following naming convention:
+
+- `feature/<issue>/<feature-name>` - For new features.
+- `fix/<issue>/<fix-name>` - For bug fixes.
+- `chore/<issue>/<chore-name>` - For miscellaneous changes.
+- `docs/<issue>/<docs-name>` - For documentation changes.
+- `test/<issue>/<test-name>` - For test changes.
+- `refactor/<issue>/<refactor-name>` - For refactoring changes.
+- `ci/<issue>/<ci-name>` - For CI/CD changes.
+
+*`/<issue>` can be omitted if there is no related issue.*
+
+### Code of Conduct
+
+Review our [Code of Conduct](CODE_OF_CONDUCT.md) to understand the expected behavior within our community.
+
+### Need Help?
+
+If you have any questions or need clarification, try opening an issue in the repository. We will be happy to help!  
+We will try to respond as quickly as possible, but please be patient.