diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md deleted file mode 100644 index ea11ad48..00000000 --- a/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,77 +0,0 @@ -# Contributor Covenant Code of Conduct - -## Our Pledge - -In the interest of fostering an open and welcoming environment, we as -contributors and maintainers pledge to making participation in our project and -our community a harassment-free experience for everyone, regardless of age, body -size, 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. - -## Our Standards - -Examples of behavior that contributes to creating a positive environment -include: - -- Using welcoming and inclusive language -- Being respectful of differing viewpoints and experiences -- Gracefully accepting constructive criticism -- Focusing on what is best for the community -- Showing empathy towards other community members - -Examples of unacceptable behavior by participants include: - -- The use of sexualized language or imagery and unwelcome sexual attention or - advances -- Trolling, insulting/derogatory comments, and personal or political attacks -- Public or private harassment -- Publishing others' private information, such as a physical or electronic - address, without explicit permission -- Other conduct which could reasonably be considered inappropriate in a - professional setting - -## Our Responsibilities - -Project maintainers are responsible for clarifying the standards of acceptable -behavior and are expected to take appropriate and fair corrective action in -response to any instances of unacceptable behavior. - -Project maintainers 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, or to ban temporarily or -permanently any contributor for other behaviors that they deem inappropriate, -threatening, offensive, or harmful. - -## Scope - -This Code of Conduct applies both within project spaces and in public spaces -when an individual is representing the project or its community. Examples of -representing a project or community include using an official project e-mail -address, posting via an official social media account, or acting as an appointed -representative at an online or offline event. Representation of a project may be -further defined and clarified by project maintainers. - -## Enforcement - -Instances of abusive, harassing, or otherwise unacceptable behavior may be -reported by contacting the project team at -[support@github.com](mailto:support@github.com). All complaints will be -reviewed and investigated and will result in a response that is deemed -necessary and appropriate to the circumstances. The project team is obligated -to maintain confidentiality with regard to the reporter of an incident. -Further details of specific enforcement policies may be posted separately. - -Project maintainers who do not follow or enforce the Code of Conduct in good -faith may face temporary or permanent repercussions as determined by other -members of the project's leadership. - -## Attribution - -This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, -available at - -[homepage]: https://www.contributor-covenant.org - -For answers to common questions about this code of conduct, see - diff --git a/SECURITY.md b/SECURITY.md deleted file mode 100644 index 6842b37a..00000000 --- a/SECURITY.md +++ /dev/null @@ -1,34 +0,0 @@ -# Security policy - -Thanks for helping make `setup-beam` safer for everyone. - -Find below updated information on our security policy. - -## Security - -We take the security of this software seriously. - -We don't implement a bug bounty program or bounty rewards, but will work with -you to ensure that your findings get the appropriate handling. - -## Reporting Security Issues - -If you believe you have found a security vulnerability in this repository, -please report it to . - -Please do not report security vulnerabilities through public channels, like -GitHub issues, discussions, or pull requests. - -Please include as much of the information listed below as you can to help us -better understand and resolve the issue: - -- the type of issue (e.g., buffer overflow, SQL injection, or cross-site - scripting) -- full paths of source file(s) related to the manifestation of the issue -- the location of the affected source code (tag/branch/commit or direct URL) -- any special configuration required to reproduce the issue -- step-by-step instructions to reproduce the issue -- proof-of-concept or exploit code (if possible) -- impact of the issue, including how an attacker might exploit the issue - -This information will help us triage your report more quickly.