nice bits

Author: Antony Bailey

CODE_OF_CONDUCT.md

@@ -0,0 +1,70 @@
+# Code of Conduct
+
+## Our Pledge
+
+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, 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.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* 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
+
+Examples of unacceptable behavior include:
+
+* 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
+
+## Enforcement Responsibilities
+
+Project maintainers 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.
+
+## Scope
+
+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.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the project maintainers responsible for enforcement at
+support@antonybailey.net. All complaints will be reviewed and investigated
+promptly and fairly.
+
+All project maintainers are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+[homepage]: https://www.contributor-covenant.org

SECURITY.md

@@ -0,0 +1,50 @@
+# Security Policy
+
+## Supported Versions
+
+Use this section to tell people about which versions of your project are
+currently being supported with security updates.
+
+| Version | Supported          |
+| ------- | ------------------ |
+| 0.1.x   | :white_check_mark: |
+
+## Reporting a Vulnerability
+
+The pySQLY team takes security issues seriously. We appreciate your efforts
+to responsibly disclose your findings and will make every effort to acknowledge
+your contributions.
+
+To report a security issue, please email support@antonybailey.net with a
+description of the issue, the steps you took to create the issue, affected
+versions, and if known, mitigations for the issue.
+
+We aim to respond to security reports within 48 hours. If for some reason you
+don't get a response within that timeframe, please follow up via email to ensure
+we received your original message.
+
+After the initial reply to your report, the security team will keep you informed
+of the progress towards a fix and full announcement, and may ask for additional
+information or guidance.
+
+## Security Best Practices for Using pySQLY
+
+When using pySQLY in your applications, consider these security best practices:
+
+1. **Always sanitize user inputs**: While pySQLY helps prevent SQL injection by
+   using parameterized queries, it's still important to validate and sanitize all
+   user inputs before processing them.
+
+2. **Use principle of least privilege**: Configure your database users with
+   the minimum required permissions for your application to function.
+
+3. **Keep dependencies updated**: Regularly update pySQLY and its dependencies
+   to ensure you have the latest security patches.
+
+4. **Store connection strings securely**: Never hard-code database credentials in
+   your source code. Use environment variables or a secure secret management system.
+
+5. **Log responsibly**: Be careful not to log sensitive information like queries
+   that might contain personal data or credentials.
+
+Thank you for helping keep pySQLY and its community safe!