We as members, contributors, and leaders pledge to make participation in our community 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, color, 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.
- Demonstrating empathy and kindness toward other people
- Being respectful of differing opinions, viewpoints, and experiences
- Giving and gracefully accepting constructive feedback
- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
- Focusing on what is best not just for us as individuals, but for the overall community
- Using welcoming and inclusive language
- Being respectful of differing viewpoints and experiences
- Showing empathy towards other community members
- The use of sexualized 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
- Publishing others' private information, such as a physical or email address, without their explicit permission
- Other conduct which could reasonably be considered inappropriate in a professional setting
- Advocating for, or encouraging, any of the above behavior
Vigil Guard is a defensive security platform designed to protect LLM applications from prompt injection attacks and malicious content.
This project contains examples of prompt injection attacks, malicious patterns, and security testing scenarios. These materials are provided exclusively for:
- Defensive security research - Understanding attack vectors to build better defenses
- Educational purposes - Learning about LLM security threats and mitigations
- Testing and validation - Verifying detection accuracy and system robustness
- Contributing to security - Improving detection rules and sanitization policies
Contributors and users must NOT:
- Use attack examples against production systems without explicit authorization
- Weaponize detection bypass techniques for malicious purposes
- Share vulnerabilities publicly before responsible disclosure (see SECURITY.md)
- Attempt to circumvent security controls in live LLM applications
- Use this platform to facilitate credential harvesting, data exfiltration, or unauthorized access
- Deploy Vigil Guard in ways that violate privacy laws or ethical guidelines
If you discover a security vulnerability in Vigil Guard itself:
- DO NOT open a public GitHub issue
- Review our Security Policy for responsible disclosure procedures
- Contact maintainers privately with details
- Allow reasonable time for patching before public disclosure
- Follow coordinated disclosure practices
Attack examples in documentation (e.g., Ignore all previous instructions) are provided for educational purposes only. These examples help developers understand:
- How prompt injection attacks work
- What patterns Vigil Guard detects
- How to configure detection thresholds appropriately
Using these examples against systems you do not own or have authorization to test is unethical and likely illegal.
Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
This Code of Conduct also applies to actions taken outside of these spaces when those actions have the potential to adversely affect the safety and well-being of community members.
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at:
- GitHub Issues: Report a concern (for non-sensitive matters)
- Email: Contact maintainers (for sensitive reports)
All complaints will be reviewed and investigated promptly and fairly.
All community leaders are obligated to respect the privacy and security of the reporter of any incident.
Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
Community Impact: A violation through a single incident or series of actions.
Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. 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.
Community Impact: A serious violation of community standards, including sustained inappropriate behavior.
Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. 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.
Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, 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.
Additional enforcement for security-related violations:
- First offense (minor): Written warning and educational resources
- Second offense (moderate): Temporary ban (30-90 days) and required security ethics training
- Severe offense: Permanent ban and potential reporting to relevant authorities
- Using attack examples against unauthorized systems
- Weaponizing bypass techniques
- Facilitating malicious use of security research
- Violating responsible disclosure policies
This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
Community Impact Guidelines were inspired by Mozilla's code of conduct enforcement ladder.
For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.
For questions about this Code of Conduct, please:
- Open a discussion in GitHub Discussions
- Review our Contributing Guide
- Consult our Security Policy for security-related concerns
Remember: Vigil Guard exists to make AI systems safer. Our community's strength lies in ethical security research, collaborative improvement, and responsible disclosure practices. Thank you for helping us maintain a welcoming and secure environment for all contributors.