feat(hsh): Initial commit

Author: sebastienrousseau

.deepsource.toml

@@ -0,0 +1,8 @@
+version = 1
+
+[[analyzers]]
+name = "rust"
+enabled = true
+
+  [analyzers.meta]
+  msrv = "stable"

.github/CODE-OF-CONDUCT.md

@@ -0,0 +1,76 @@
+# 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 behaviour 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 behaviour 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 behaviour and are expected to take appropriate and fair
+corrective action in response to any instances of unacceptable
+behaviour.
+
+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 behaviour may
+be reported by contacting the project team. The project team will review
+and investigate all complaints, and will respond in a way that it deems
+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
+[version](http://contributor-covenant.org/version/1/4)

.github/CODEOWNERS

@@ -0,0 +1 @@
+@sebastienrousseau/hsh

.github/CONTRIBUTING.md

@@ -0,0 +1,67 @@
+# Contributing
+
+Thank you so much for wanting to contribute to Common (CMN)!
+There are a couple ways to help out.
+
+## Evangelize
+
+Just tell people about Common (CMN). We believe that a bigger,
+more involved community makes for a better framework, and that better
+frameworks make the world a better place. We can always use more
+feedback.
+
+## How to Contribute
+
+Here are guides for submitting issues and pull requests.
+
+### Bug Reports
+
+If you encounter a bug that hasn't already been filed, please file a
+bug report. Let us know of things we should fix, things we should add,
+questions, etc.
+
+Warning us of a bug is possibly the single most valuable contribution
+you can make to Common (CMN).
+
+- Head
+  [here](https://github.com/sebastienrousseau/mini-functions/issues/new)
+  to submit a new issue.
+- Include a descriptive title that is straight to the point.
+- Write a detailed description on what the issue is all about.
+- Wait for someone to get to the issue and add labels.
+- The issue will be fixed soon!
+
+### Code Contributions
+
+Contributing code is one of the more difficult ways to contribute to the
+Mini Functions.
+
+#### Feature Requests
+
+Filing feature requests is one of the most popular ways to contribute to
+Common (CMN).
+
+Is there some feature request that you'd like to code up yourself? Is
+there a feature you asked for yourself that you'd like to code?
+
+Here's how to contribute code for a new feature to Common (CMN).
+Pull Requests allow you to share your own code with us, and we can merge
+it into the main repo.
+
+#### Adding Code
+
+- Fork the repo.
+- Clone the Common (CMN) repo by running:
+  `git clone https://github.com/sebastienrousseau/mini-functions.git`
+- Edit files in the `src/` folder. The `src/` folder contains the source
+  code for Common (CMN).
+
+#### Fixing an Issue
+
+Have you found a solution to an issue? Here is how you can submit your
+code to Common (CMN).
+
+- Fork the repo, and refer above for how to change up code.
+- Head to your local fork of the repo and click the "New Pull Request" button.
+- Include a title that is straight to the point.
+- Wait for someone to review the pull request, and then merge yours!

.github/SECURITY.md

@@ -0,0 +1,26 @@
+# Security
+
+We take the security of our software products and services seriously,
+which includes all source code repositories managed through our GitHub
+repositories.
+
+If you believe you have found a security vulnerability in any of our
+repository, please report it to us as described below.
+
+## Reporting Security Issues
+
+Please include the requested information listed below (as much as you
+can provide) to help us better understand the nature and scope of the
+possible issue:
+
+- Type of issue (e.g. buffer overflow, SQL injection, cross-site
+  scripting, etc.)
+- 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.

.github/dependabot.yml

@@ -0,0 +1,11 @@
+version: 2
+updates:
+  - package-ecosystem: "cargo"
+    directory: "/"
+    schedule:
+      interval: "daily"
+
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "daily"

.github/funding.yml

@@ -0,0 +1,2 @@
+github: sebastienrousseau
+custom: https://paypal.me/wwdseb