crucible-security 0.1.0__tar.gz

crucible_security-0.1.0/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,29 @@
+---
+name: Bug Report
+about: Report a bug to help us improve Crucible
+title: "[BUG] "
+labels: bug
+assignees: ''
+---
+
+## Describe the Bug
+A clear and concise description of what the bug is.
+
+## Steps to Reproduce
+1. Install crucible: `pip install crucible-security`
+2. Run: `crucible scan --target ...`
+3. See error
+
+## Expected Behavior
+What you expected to happen.
+
+## Actual Behavior
+What actually happened. Include the full error traceback if applicable.
+
+## Environment
+- OS: [e.g., Ubuntu 22.04, Windows 11, macOS 14]
+- Python version: [e.g., 3.12.1]
+- Crucible version: [run `crucible --version`]
+
+## Additional Context
+Add any other context about the problem here.

crucible_security-0.1.0/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature Request
+about: Suggest an idea for Crucible
+title: "[FEATURE] "
+labels: enhancement
+assignees: ''
+---
+
+## Use Case
+Describe the problem or use case that this feature would address.
+What are you trying to accomplish?
+
+## Proposed Solution
+Describe the solution you'd like to see implemented.
+
+## Alternatives Considered
+Any alternative solutions or features you've considered.
+
+## Additional Context
+Add any other context, mockups, or references.

crucible_security-0.1.0/.github/ISSUE_TEMPLATE/new_attack.md

@@ -0,0 +1,45 @@
+---
+name: New Attack Vector
+about: Propose a new attack vector for Crucible
+title: "[ATTACK] "
+labels: new-attack
+assignees: ''
+---
+
+## Attack Name
+What should this attack be called? (e.g., "Context Window Overflow")
+
+## OWASP Category
+Which OWASP Agentic Top 10 category does this fall under?
+- [ ] Goal Hijacking
+- [ ] Prompt Injection
+- [ ] Tool Misuse
+- [ ] Identity Abuse
+- [ ] Memory Poisoning
+- [ ] Data Exfiltration
+- [ ] Scope Violation
+- [ ] Cascading Failure
+- [ ] Supply Chain
+- [ ] Rogue Agent
+
+## Severity
+- [ ] CRITICAL
+- [ ] HIGH
+- [ ] MEDIUM
+- [ ] LOW
+
+## Description
+Describe the attack technique and what vulnerability it exposes.
+
+## Example Payloads
+Provide 2-3 example payloads:
+```
+Payload 1: "..."
+Payload 2: "..."
+```
+
+## Detection Criteria
+How should Crucible determine if the attack succeeded (vulnerability found)?
+
+## References
+Links to papers, blog posts, or documentation about this attack.

crucible_security-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,71 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+permissions:
+  contents: read
+
+jobs:
+  lint:
+    name: Lint & Type Check
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.9", "3.10", "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: |
+          python -m pip install --upgrade pip
+          pip install -e ".[dev]"
+
+      - name: Black (formatting)
+        run: black --check crucible/ tests/
+
+      - name: Ruff (linting)
+        run: ruff check crucible/ tests/
+
+      - name: Mypy (type checking)
+        run: mypy crucible/
+
+  test:
+    name: Test Suite
+    runs-on: ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: [ubuntu-latest, windows-latest, macos-latest]
+        python-version: ["3.9", "3.10", "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: |
+          python -m pip install --upgrade pip
+          pip install -e ".[dev]"
+
+      - name: Run tests with coverage
+        run: pytest tests/ -v --cov=crucible --cov-report=xml
+
+      - name: Upload coverage to Codecov
+        if: matrix.os == 'ubuntu-latest' && matrix.python-version == '3.12'
+        uses: codecov/codecov-action@v4
+        with:
+          file: ./coverage.xml
+          fail_ci_if_error: false

crucible_security-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,54 @@
+name: Publish to PyPI
+
+on:
+  release:
+    types: [published]
+
+permissions:
+  contents: read
+  id-token: write
+
+jobs:
+  build:
+    name: Build Distribution
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install build tools
+        run: |
+          python -m pip install --upgrade pip
+          pip install build
+
+      - name: Build package
+        run: python -m build
+
+      - name: Upload artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    name: Publish to PyPI
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/p/crucible-security
+
+    steps:
+      - name: Download artifacts
+        uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

crucible_security-0.1.0/.gitignore

@@ -0,0 +1,207 @@
+# 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__/

crucible_security-0.1.0/CHANGELOG.md

@@ -0,0 +1,28 @@
+# Changelog
+
+All notable changes to Crucible will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.1.0] - 2026-04-21
+
+### Added
+- Core Pydantic data models: `AgentTarget`, `Finding`, `ModuleResult`, `ScanResult`
+- 50 prompt injection attack vectors (PI-001 through PI-050)
+- 20 goal hijacking attack vectors (GH-001 through GH-020)
+- 20 jailbreak attack vectors (JB-001 through JB-020)
+- Security modules: `PromptInjectionModule`, `GoalHijackingModule`, `JailbreakModule`
+- Async scan runner with parallel module execution via `anyio`
+- CVSS-inspired scoring engine with letter grading (A+ through F)
+- Rich terminal reporter with color-coded findings and score visualization
+- JSON reporter for CI/CD integration
+- Typer CLI with `init`, `scan`, and `report` commands
+- Full type annotations with strict mypy compliance
+- Comprehensive test suite (88%+ coverage)
+- GitHub Actions CI/CD pipelines (lint, test, publish)
+
+[Unreleased]: https://github.com/crucible-security/crucible/compare/v0.1.0...HEAD
+[0.1.0]: https://github.com/crucible-security/crucible/releases/tag/v0.1.0

crucible_security-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,165 @@
+# Contributing to Crucible
+
+Thank you for your interest in contributing to Crucible! This guide will help you get started.
+
+## Development Setup
+
+### Prerequisites
+
+- Python 3.9+
+- Git
+
+### Installation
+
+```bash
+# Clone the repository
+git clone https://github.com/crucible-security/crucible.git
+cd crucible
+
+# Create a virtual environment
+python -m venv .venv
+source .venv/bin/activate  # Linux/Mac
+# .venv\Scripts\activate   # Windows
+
+# Install in development mode
+pip install -e ".[dev]"
+```
+
+### Verify Installation
+
+```bash
+crucible --help
+crucible --version
+```
+
+## Development Workflow
+
+### Code Quality
+
+We enforce strict code quality standards. Before submitting a PR, ensure:
+
+```bash
+# Format code
+black crucible/ tests/
+
+# Lint
+ruff check crucible/ tests/
+
+# Type check (strict mode)
+mypy crucible/
+
+# Run tests
+pytest tests/ -v --cov=crucible
+```
+
+### Running a Scan
+
+```bash
+# Generate a config scaffold
+crucible init
+
+# Run a scan
+crucible scan --target https://your-agent.com/api --name "My Agent"
+```
+
+## Architecture
+
+```
+crucible/
+  __init__.py           # Package root, public API
+  models.py             # Pydantic data models
+  cli.py                # Typer CLI interface
+  attacks/
+    base.py             # BaseAttack ABC
+    prompt_injection.py # 50 PI attack vectors
+    goal_hijacking.py   # 20 GH attack vectors
+    jailbreaks.py       # 20 JB attack vectors
+  modules/
+    base.py             # BaseModule ABC
+    security.py         # Module registry
+  core/
+    runner.py           # Async scan runner (anyio)
+    scorer.py           # Scoring + grading engine
+  reporters/
+    terminal.py         # Rich terminal output
+    json_reporter.py    # JSON file export
+tests/
+  conftest.py           # Shared fixtures
+  test_models.py        # Model validation tests
+  test_scorer.py        # Scoring engine tests
+  test_attacks.py       # Attack + module tests
+  test_cli.py           # CLI integration tests
+```
+
+## Adding a New Attack
+
+1. Create a new class in the appropriate attack module (e.g., `prompt_injection.py`):
+
+```python
+class MyNewAttack(BaseAttack):
+    name = "PI-051"
+    title = "My New Attack"
+    category = AttackCategory.PROMPT_INJECTION
+    severity = Severity.HIGH
+    description = "What this attack tests."
+    remediation = "How to fix the vulnerability."
+
+    def get_payloads(self) -> list[str]:
+        return ["payload 1", "payload 2"]
+
+    def get_detection_patterns(self) -> list[str]:
+        return ["pattern_to_detect"]
+```
+
+2. Add the class to the attack registry list (e.g., `ALL_PROMPT_INJECTION_ATTACKS`).
+3. Add tests in `test_attacks.py`.
+4. Run the quality gate: `black`, `mypy`, `pytest`.
+
+## Adding a New Module
+
+1. Create a new class in `crucible/modules/security.py`:
+
+```python
+class MyModule(BaseModule):
+    name = "my_module"
+    description = "Description of what this module tests."
+    category = AttackCategory.PROMPT_INJECTION
+
+    def get_attacks(self) -> list[BaseAttack]:
+        return [MyAttack1(), MyAttack2()]
+```
+
+2. Add it to `ALL_SECURITY_MODULES`.
+3. Add tests in `test_attacks.py`.
+
+## Pull Request Guidelines
+
+- **One PR per feature/fix** -- keep changes focused.
+- **Include tests** for all new functionality.
+- **Pass all quality gates** before requesting review.
+- **Write descriptive commit messages** following [Conventional Commits](https://www.conventionalcommits.org/).
+- **Update CHANGELOG.md** with your changes under `[Unreleased]`.
+
+## Commit Message Format
+
+```
+<type>: <description>
+
+feat: add new XSS attack vectors
+fix: handle timeout in scan runner
+test: add scorer edge case tests
+docs: update contributing guide
+```
+
+## Reporting Issues
+
+Use [GitHub Issues](https://github.com/crucible-security/crucible/issues) to report bugs or request features. Please include:
+
+- Steps to reproduce
+- Expected vs. actual behavior
+- Python version and OS
+- Crucible version (`crucible --version`)
+
+## License
+
+By contributing, you agree that your contributions will be licensed under the [Apache 2.0 License](LICENSE).