Adding initial 0.1.0 release files.

Author: AzorianMatt

.github/ACKNOWLEDGMENTS.md

@@ -0,0 +1,3 @@
+# ADPeeper
+
+## Acknowledgments

.github/AUTHORS.md

@@ -0,0 +1,13 @@
+# PDA Next
+
+## Authors
+
+This is the list of the ADPeeper application's significant contributors.
+
+This does not necessarily list everyone who has contributed code,
+especially since many employees of one corporation may be contributing.
+
+To see the full list of contributors, see the revision history in
+source control.
+
+- <a href="https://azorian.solutions" target="_blank">Azorian Solutions LLC</a> &lt;<a href="mailto:help@azorian.solutions">help@azorian.solutions</a>&gt;

.github/CODEOWNERS.md

@@ -0,0 +1,3 @@
+# Code Owners
+
+- <a href="https://azorian.solutions" target="_blank">Azorian Solutions LLC</a> &lt;<a href="mailto:help@azorian.solutions">help@azorian.solutions</a>&gt;

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# 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, gender identity and expression, level of experience,
+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 [admin@powerdnsadmin.org](mailto:admin@powerdnsadmin.org). 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 [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

.github/CONTRIBUTING.md

@@ -0,0 +1,3 @@
+# Contributing Guide
+
+Contributions are not currently being accepted for this project.

.github/CONTRIBUTORS.md

@@ -0,0 +1,11 @@
+# Contributors
+
+This is a list of people / organizations that are currently contributing to the project in
+some way.
+
+This does not necessarily list everyone who has contributed code.
+
+To see the full list of contributors, see the revision history in
+source control.
+
+- <a href="https://azorian.solutions" target="_blank">Azorian Solutions LLC</a> &lt;<a href="mailto:help@azorian.solutions">help@azorian.solutions</a>&gt;

.github/FUNDING.md

@@ -0,0 +1,3 @@
+# Funding
+
+**Want to sponsor me?** Please visit my organization's [sponsorship page](https://github.com/sponsors/AzorianSolutions).

.github/FUNDING.yml

@@ -0,0 +1 @@
+github: [AzorianSolutions]

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,14 @@
+<!--
+    Thank you for your interest in contributing to the ADPeeper project! Please note that our contribution
+    policy requires that a feature request or bug report be approved and assigned prior to opening a pull request.
+    This helps avoid wasted time and effort on a proposed change that we might want to or be able to accept.
+
+    IF YOUR PULL REQUEST DOES NOT REFERENCE AN ISSUE WHICH HAS BEEN ASSIGNED TO YOU, IT WILL BE CLOSED AUTOMATICALLY!
+
+    Please specify your assigned issue number on the line below.
+-->
+### Fixes: #1234
+
+<!--
+    Please include a summary of the proposed changes below.
+-->

.github/SECURITY.md

@@ -0,0 +1,31 @@
+# Security Policy
+
+## No Warranty
+
+Per the terms of the MIT license, ADPeeper is offered "as is" and without any guarantee or warranty pertaining to its operation. While every reasonable effort is made by its maintainers to ensure the product remains free of security vulnerabilities, users are ultimately responsible for conducting their own evaluations of each software release.
+
+## Recommendations
+
+Administrators are encouraged to adhere to industry best practices concerning the secure operation of software, such as:
+
+* Do not expose your ADPeeper installation to the public Internet
+* Do not permit multiple users to share an account
+* Enforce minimum password complexity requirements for local accounts
+* Prohibit access to your database from clients other than the ADPeeper application
+* Keep your deployment updated to the most recent stable release
+
+## Reporting a Suspected Vulnerability
+
+If you believe you've uncovered a security vulnerability and wish to report it confidentially, you may do so via email. Please note that any reported vulnerabilities **MUST** meet all the following conditions:
+
+* Affects the most recent stable release of ADPeeper, or a current beta release
+* Affects a ADPeeper instance installed and configured per the official documentation
+* Is reproducible following a prescribed set of instructions
+
+Please note that we **DO NOT** accept reports generated by automated tooling which merely suggest that a file or file(s) _may_ be vulnerable under certain conditions, as these are most often innocuous.
+
+If you believe that you've found a vulnerability which meets all of these conditions, please [submit a draft security advisory](https://github.com/AzorianSolutions/adpeeper/security/advisories/new) on GitHub, or email a brief description of the suspected bug and instructions for reproduction to **security@azorian.solutions**.
+
+### Bug Bounties
+
+As ADPeeper is provided as free open source software, we do not offer any monetary compensation for vulnerability or bug reports, however your contributions are greatly appreciated.