Need help with Keyspace? We're here to help!
Start with our comprehensive documentation:
- Quick Start Guide - Get started in 5 minutes
- User Guide - Complete usage documentation
- FAQ - Frequently asked questions
- API Documentation - For developers
Join our community for help and discussions:
- GitHub Discussions: github.com/tworjaga/keyspace/discussions
- Discord: discord.gg/keyspace
- Stack Overflow: Tag your questions with
keyspace
Found a bug? Please report it:
- Check if it's already reported in Issues
- If not, create a new issue
- Use the bug report template and provide as much detail as possible
Have an idea? We'd love to hear it:
- Check if it's already requested in Issues
- If not, create a feature request
- Describe your use case and the feature you'd like to see
- GitHub Issues (bug reports and feature requests)
- GitHub Discussions (Q&A and general discussion)
- Discord community chat
- Stack Overflow (programming questions)
For enterprise users requiring dedicated support:
-
Email: support@keyspace.example.com
-
Priority Response: 24-hour response time
-
Custom Development: Feature development and customization
-
Training: On-site or remote training sessions
-
Consulting: Security assessment and implementation guidance
Contact us at enterprise@keyspace.example.com for commercial support options.
- Installation and setup issues
- Configuration problems
- Bug reports and feature requests
- Usage questions
- Performance optimization
- Integration guidance
- Security best practices
- Cracking passwords you don't own or have permission to test
- Bypassing security systems illegally
- Recovering lost passwords for third-party services
- Any illegal or unethical activities
Please check these items before reaching out:
- Read the documentation - Your question might already be answered
- Search existing issues - Someone might have had the same problem
- Check your version - Make sure you're using the latest version
- Try the basics - Restart the application, check your configuration
- Gather information - Collect error messages, logs, and system info
When reporting issues, please include:
-
Keyspace version
-
Operating system and version
-
Python version
-
Steps to reproduce the issue
-
Expected behavior
-
Actual behavior
-
Error messages (full traceback if available)
-
Screenshots (if applicable)
- System specifications (CPU, RAM, GPU)
- Attack type and configuration
- Target type and hash
- Wordlist size (if applicable)
- Performance metrics (speed, memory usage)
- Operating system and version
- Installation method (pip, package, source)
- Python version
- Error messages during installation
- Dependencies installed
- Critical bugs: 24-48 hours
- Feature requests: 1-2 weeks (evaluation)
- General questions: 2-5 days
- Documentation issues: 1-2 weeks
DO NOT report security vulnerabilities publicly.
Instead:
-
Or use GitHub Security Advisories
-
Include detailed description and reproduction steps
-
Allow time for fix before public disclosure
See SECURITY.md for our security policy.
- Beginner Workshop: 2-hour introduction
- Advanced Training: Full-day deep dive
- Custom Training: Tailored to your needs
- Security assessment
- Implementation planning
- Custom feature development
- Integration architecture
| Tier | Response Time | Channels | Price |
|---|---|---|---|
| Community | Best effort | GitHub, Discord | Free |
| Basic | 48 hours | $99/month | |
| Professional | 24 hours | Email, Phone | $299/month |
| Enterprise | 4 hours | Dedicated manager | Custom |
Contact enterprise@keyspace.example.com for details.
Help others in the community:
- Answer questions on GitHub Discussions
- Share your solutions
- Write tutorials and blog posts
- Improve documentation
We value your feedback:
- Rate your experience: Feedback Form
- Suggest improvements: GitHub Discussions
- Report documentation issues: GitHub Issues
Thank you for using Keyspace!
We're committed to helping you succeed with your security testing needs.