Thank you for your interest in contributing to Certipy! Whether you're reporting a bug, improving documentation, or submitting a pull request - your help is appreciated.
Please use the appropriate issue template when opening a new issue:
- 🐞 Bug Reports: Include the version, OS, the exact command used (redacted if needed), error output, and any relevant
certipy findinfo. - 🙋 Help Requests: For general questions or clarification on usage, not tied to a specific error.
- ✨ Feature Requests: Describe the feature, your use case, and any alternatives or examples.
👉 Issue templates will guide you when you open an issue.
Certipy uses:
blackfor code formattingisortfor import sorting (configured for black compatibility)pyrightfor type checkingflake8for linting
# Setup virtual environment
python3 -m venv venv
source venv/bin/activate
# Install dev dependencies
pip install -e .
pip install black isort pyright flake8 pep8-namingflake8 ./certipy && isort . && black . && pyright- Fork the repo and create a branch:
git checkout -b feature/my-feature-name - Follow the coding standards above
- Keep PRs small and focused
- Include a brief description of why the change is useful
- Link to any relevant issues (e.g.,
Fixes #123) - Run tests (if applicable)
- Explain how to test the changes, setting up the environment, and any dependencies
- Submit your PR for review!
You can help improve the documentation! To do so:
-
Clone the wiki repo directly:
git clone https://github.com/ly4k/Certipy.wiki.git
-
Make your changes in
*.mdfiles (e.g.,ESC1.md,Home.md) -
Submit a pull request or send a patch if you're not a collaborator
-
Use Markdown preview tools (like VSCode or
grip) to review your changes
Tip
For private drafts, maintain a local folder or branch and sync it later to the public .wiki.git.
Feel free to open a Help Request - just be clear about what you’re trying to accomplish and what you’ve tried.
Thanks again for supporting Certipy!
– @ly4k