Updated repo meta

.github/pull_request_template.md

@@ -2,7 +2,7 @@
 
 Thank you for taking the time to contribute to Signale!
 
-For more info on how to contribute to the project, please read the [contributing guidelines](https://github.com/klauscfhq/signale/blob/master/contributing.md).
+For more info on how to contribute to the project, please read the [contributing guidelines](https://github.com/klaussinani/signale/blob/master/contributing.md).
 
 We are always excited about pull requests!
 If the pull request fixes any open issues, reference the corresponding issues in the following fashion: `Fixes #321`.

code-of-conduct.md

@@ -34,7 +34,7 @@ This Code of Conduct applies both within project spaces and in public spaces whe
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at klauscfhq@protonmail.com. 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.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at klaussinani@gmail.com. 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.
 

contributing.md

@@ -8,7 +8,7 @@ Please note that this project is released with a [Contributor Code of Conduct](c
 
 ### Improve documentation
 
-Typo corrections, error fixes, better explanations, more examples etc. Open an issue regarding anything that you think it could be improved! You can use the [`docs` label](https://github.com/klauscfhq/signale/labels/docs) to find out what others have suggested!
+Typo corrections, error fixes, better explanations, more examples etc. Open an issue regarding anything that you think it could be improved! You can use the [`docs` label](https://github.com/klaussinani/signale/labels/docs) to find out what others have suggested!
 
 ### Improve issues
 
@@ -18,36 +18,36 @@ Sometimes reported issues lack information, are not reproducible, or are even pl
 
 We're always looking for more opinions on discussions in the issue tracker. It's a good opportunity to influence the future direction of the project.
 
-The [`question` label](https://github.com/klauscfhq/signale/labels/question) is a good place to find ongoing discussions.
+The [`question` label](https://github.com/klaussinani/signale/labels/question) is a good place to find ongoing discussions.
 
 ### Write code
 
 You can use issue labels to discover issues you could help us out with!
 
-- [`feature request` issues](https://github.com/klauscfhq/signale/labels/feature%20request) are features we are open to including
-- [`bug` issues](https://github.com/klauscfhq/signale/labels/bug) are known bugs we would like to fix
-- [`future` issues](https://github.com/klauscfhq/signale/labels/future) are those that we'd like to get to, but not anytime soon. Please check before working on these since we may not yet want to take on the burden of supporting those features
-- on the [`help wanted`](https://github.com/klauscfhq/signale/labels/help%20wanted) label you can always find something exciting going on
+- [`feature request` issues](https://github.com/klaussinani/signale/labels/feature%20request) are features we are open to including
+- [`bug` issues](https://github.com/klaussinani/signale/labels/bug) are known bugs we would like to fix
+- [`future` issues](https://github.com/klaussinani/signale/labels/future) are those that we'd like to get to, but not anytime soon. Please check before working on these since we may not yet want to take on the burden of supporting those features
+- on the [`help wanted`](https://github.com/klaussinani/signale/labels/help%20wanted) label you can always find something exciting going on
 
-You may find an issue is assigned, or has the [`assigned` label](https://github.com/klauscfhq/signale/labels/assigned). Please double-check before starting on this issue because somebody else is likely already working on it
+You may find an issue is assigned, or has the [`assigned` label](https://github.com/klaussinani/signale/labels/assigned). Please double-check before starting on this issue because somebody else is likely already working on it
 
 ### Say hi
 
-Come over and say hi anytime you feel like on [Gitter](https://gitter.im/klauscfhq/signale).
+Come over and say hi anytime you feel like on [Gitter](https://gitter.im/klaussinani/signale).
 
 ### Translating Documentation
 
 #### Create a Translation
 
-- Visit the [`translations' index`](https://github.com/klauscfhq/signale/tree/master/docs/readme.md) file to ensure that the document is not already translated in your target language. 
+- Visit the [`translations' index`](https://github.com/klaussinani/signale/tree/master/docs/readme.md) file to ensure that the document is not already translated in your target language. 
 - Add the name of the language to the document as an extension, e.g: `readme.JP.md`
-- Place the translated document inside the [`docs`](https://github.com/klauscfhq/signale/tree/master/docs) directory.
-- Add your github profile and the translated document at the [`translations' index`](https://github.com/klauscfhq/signale/tree/master/docs/readme.md) file.
+- Place the translated document inside the [`docs`](https://github.com/klaussinani/signale/tree/master/docs) directory.
+- Add your github profile and the translated document at the [`translations' index`](https://github.com/klaussinani/signale/tree/master/docs/readme.md) file.
 - Create a Pull Request including the language in the title, e.g: `Readme: Japanese Translation`
 
 #### Improve a Translation
 
-- Include your github profile next to the translation you improved at the [`translations' index`](https://github.com/klauscfhq/signale/tree/master/docs/readme.md) file.
+- Include your github profile next to the translation you improved at the [`translations' index`](https://github.com/klaussinani/signale/tree/master/docs/readme.md) file.
 - Create a Pull Request that delivers the improvements and include the language in the title, e.g: `Readme: Improvements for the Japanese Translation`
 
 ### Submitting an issue

license.md

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) Klaus Sinani <klauscfhq@protonmail.com>
+Copyright (c) Klaus Sinani <klaussinani@gmail.com>
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

package.json

@@ -3,11 +3,11 @@
   "version": "1.3.0",
   "description": "👋 Hackable console logger",
   "license": "MIT",
-  "repository": "klauscfhq/signale",
+  "repository": "klaussinani/signale",
   "author": {
     "name": "Klaus Sinani",
-    "email": "klauscfhq@protonmail.com",
-    "url": "https://klauscfhq.github.io"
+    "email": "klaussinani@gmail.com",
+    "url": "https://klaussinani.github.io"
   },
   "maintainers": [
     {