fastapi-myauth 0.1.0__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (72) hide show
  1. fastapi_myauth-0.1.0/.devcontainer/devcontainer.json +44 -0
  2. fastapi_myauth-0.1.0/.github/CODEOWNERS +6 -0
  3. fastapi_myauth-0.1.0/.github/CODE_OF_CONDUCT.md +76 -0
  4. fastapi_myauth-0.1.0/.github/CONTRIBUTING.md +23 -0
  5. fastapi_myauth-0.1.0/.github/FUNDING.yml +1 -0
  6. fastapi_myauth-0.1.0/.github/ISSUE_TEMPLATE/1-bug-report.md +79 -0
  7. fastapi_myauth-0.1.0/.github/ISSUE_TEMPLATE/2-failing-test.md +41 -0
  8. fastapi_myauth-0.1.0/.github/ISSUE_TEMPLATE/3-docs-bug.md +60 -0
  9. fastapi_myauth-0.1.0/.github/ISSUE_TEMPLATE/4-feature-request.md +45 -0
  10. fastapi_myauth-0.1.0/.github/ISSUE_TEMPLATE/5-enhancement-request.md +45 -0
  11. fastapi_myauth-0.1.0/.github/ISSUE_TEMPLATE/6-security-report.md +100 -0
  12. fastapi_myauth-0.1.0/.github/ISSUE_TEMPLATE/7-question-support.md +28 -0
  13. fastapi_myauth-0.1.0/.github/ISSUE_TEMPLATE/config.yml +5 -0
  14. fastapi_myauth-0.1.0/.github/ISSUE_TEMPLATE.md +41 -0
  15. fastapi_myauth-0.1.0/.github/SECURITY.md +11 -0
  16. fastapi_myauth-0.1.0/.github/SUPPORT.md +11 -0
  17. fastapi_myauth-0.1.0/.github/config.yml +20 -0
  18. fastapi_myauth-0.1.0/.github/dependabot.yml +30 -0
  19. fastapi_myauth-0.1.0/.github/issue_label_bot.yaml +4 -0
  20. fastapi_myauth-0.1.0/.github/labeler.yml +25 -0
  21. fastapi_myauth-0.1.0/.github/pull_request_template.md +29 -0
  22. fastapi_myauth-0.1.0/.github/settings.yml +184 -0
  23. fastapi_myauth-0.1.0/.github/workflows/cd.yml +101 -0
  24. fastapi_myauth-0.1.0/.github/workflows/labeler.yml +33 -0
  25. fastapi_myauth-0.1.0/.github/workflows/lint-backend.yml +29 -0
  26. fastapi_myauth-0.1.0/.github/workflows/smokeshow.yml +35 -0
  27. fastapi_myauth-0.1.0/.github/workflows/test-backend.yml +41 -0
  28. fastapi_myauth-0.1.0/.gitignore +9 -0
  29. fastapi_myauth-0.1.0/.pre-commit-config.yaml +25 -0
  30. fastapi_myauth-0.1.0/.vscode/extensions.json +14 -0
  31. fastapi_myauth-0.1.0/.vscode/launch.json +15 -0
  32. fastapi_myauth-0.1.0/.vscode/settings.json +77 -0
  33. fastapi_myauth-0.1.0/CHANGELOG.md +9 -0
  34. fastapi_myauth-0.1.0/LICENSE +21 -0
  35. fastapi_myauth-0.1.0/Makefile +61 -0
  36. fastapi_myauth-0.1.0/PKG-INFO +15 -0
  37. fastapi_myauth-0.1.0/README.md +72 -0
  38. fastapi_myauth-0.1.0/fastapi_myauth/__init__.py +0 -0
  39. fastapi_myauth-0.1.0/fastapi_myauth/api/__init__.py +0 -0
  40. fastapi_myauth-0.1.0/fastapi_myauth/api/deps.py +153 -0
  41. fastapi_myauth-0.1.0/fastapi_myauth/api/v1/__init__.py +2 -0
  42. fastapi_myauth-0.1.0/fastapi_myauth/api/v1/login.py +364 -0
  43. fastapi_myauth-0.1.0/fastapi_myauth/api/v1/users.py +219 -0
  44. fastapi_myauth-0.1.0/fastapi_myauth/auth.py +81 -0
  45. fastapi_myauth-0.1.0/fastapi_myauth/config.py +59 -0
  46. fastapi_myauth-0.1.0/fastapi_myauth/crud/__init__.py +2 -0
  47. fastapi_myauth-0.1.0/fastapi_myauth/crud/base.py +70 -0
  48. fastapi_myauth-0.1.0/fastapi_myauth/crud/crud_token.py +41 -0
  49. fastapi_myauth-0.1.0/fastapi_myauth/crud/crud_user.py +95 -0
  50. fastapi_myauth-0.1.0/fastapi_myauth/email-templates/build/confirm_email.html +24 -0
  51. fastapi_myauth-0.1.0/fastapi_myauth/email-templates/build/magic_login.html +25 -0
  52. fastapi_myauth-0.1.0/fastapi_myauth/email-templates/build/new_account.html +194 -0
  53. fastapi_myauth-0.1.0/fastapi_myauth/email-templates/build/reset_password.html +25 -0
  54. fastapi_myauth-0.1.0/fastapi_myauth/email-templates/build/test_email.html +25 -0
  55. fastapi_myauth-0.1.0/fastapi_myauth/email-templates/build/web_contact_email.html +24 -0
  56. fastapi_myauth-0.1.0/fastapi_myauth/email-templates/src/confirm_email.mjml +52 -0
  57. fastapi_myauth-0.1.0/fastapi_myauth/email-templates/src/magic_login.mjml +54 -0
  58. fastapi_myauth-0.1.0/fastapi_myauth/email-templates/src/new_account.mjml +43 -0
  59. fastapi_myauth-0.1.0/fastapi_myauth/email-templates/src/reset_password.mjml +57 -0
  60. fastapi_myauth-0.1.0/fastapi_myauth/email-templates/src/test_email.mjml +11 -0
  61. fastapi_myauth-0.1.0/fastapi_myauth/email-templates/src/web_contact_email.mjml +20 -0
  62. fastapi_myauth-0.1.0/fastapi_myauth/email.py +123 -0
  63. fastapi_myauth-0.1.0/fastapi_myauth/models/__init__.py +14 -0
  64. fastapi_myauth-0.1.0/fastapi_myauth/models/emails.py +14 -0
  65. fastapi_myauth-0.1.0/fastapi_myauth/models/msg.py +5 -0
  66. fastapi_myauth-0.1.0/fastapi_myauth/models/token.py +45 -0
  67. fastapi_myauth-0.1.0/fastapi_myauth/models/totp.py +18 -0
  68. fastapi_myauth-0.1.0/fastapi_myauth/models/user.py +64 -0
  69. fastapi_myauth-0.1.0/fastapi_myauth/security.py +127 -0
  70. fastapi_myauth-0.1.0/fastapi_myauth/test_main.py +39 -0
  71. fastapi_myauth-0.1.0/pyproject.toml +61 -0
  72. fastapi_myauth-0.1.0/uv.lock +1148 -0
@@ -0,0 +1,44 @@
1
+ // For format details, see https://aka.ms/devcontainer.json. For config options, see the
2
+ // README at: https://github.com/devcontainers/templates/tree/main/src/typescript-node
3
+ {
4
+ "name": "FastAPI",
5
+
6
+ // Base image. More info: https://github.com/devcontainers/images
7
+ "image": "mcr.microsoft.com/devcontainers/base:debian",
8
+
9
+ // Features to add to the dev container. More info: https://containers.dev/features.
10
+ "features": {
11
+ "ghcr.io/devcontainers/features/python:1": {
12
+ "version": "3.13.2",
13
+ "toolsToInstall": "uv"
14
+ },
15
+ "ghcr.io/devcontainers/features/docker-in-docker:2": {}
16
+ },
17
+
18
+ // Use 'forwardPorts' to make a list of ports inside the container available locally.
19
+ // "forwardPorts": [],
20
+
21
+ // Use 'postCreateCommand' to run commands after the container is created.
22
+ //"postCreateCommand": "",
23
+
24
+ // Configure tool-specific properties.
25
+ "customizations": {
26
+ "vscode": {
27
+ "extensions": [
28
+ "charliermarsh.ruff",
29
+ "esbenp.prettier-vscode",
30
+ "ms-azuretools.vscode-docker",
31
+ "GitHub.copilot",
32
+ "GitHub.copilot-chat",
33
+ "eamodio.gitlens",
34
+ "ms-python.python",
35
+ "ms-python.debugpy",
36
+ "rooveterinaryinc.roo-cline",
37
+ "adam-bender.commit-message-editor"
38
+ ]
39
+ }
40
+ }
41
+
42
+ // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
43
+ // "remoteUser": "root"
44
+ }
@@ -0,0 +1,6 @@
1
+ # These owners will be the default owners for everything in
2
+ # the repo. Unless a later match takes precedence,
3
+ # @ will be requested for
4
+ # review when someone opens a pull request.
5
+ # if you want to add more owners, just write it after @
6
+ * @
@@ -0,0 +1,76 @@
1
+ # Contributor Covenant Code of Conduct
2
+
3
+ ## Our Pledge
4
+
5
+ In the interest of fostering an open and welcoming environment, we as
6
+ contributors and maintainers pledge to make participation in our project and
7
+ our community a harassment-free experience for everyone, regardless of age, body
8
+ size, disability, ethnicity, sex characteristics, gender identity and expression,
9
+ level of experience, education, socio-economic status, nationality, personal
10
+ appearance, race, religion, or sexual identity and orientation.
11
+
12
+ ## Our Standards
13
+
14
+ Examples of behaviour that contributes to creating a positive environment
15
+ include:
16
+
17
+ * Using welcoming and inclusive language
18
+ * Being respectful of differing viewpoints and experiences
19
+ * Gracefully accepting constructive criticism
20
+ * Focusing on what is best for the community
21
+ * Showing empathy towards other community members
22
+
23
+ Examples of unacceptable behaviour by participants include:
24
+
25
+ * The use of sexualized language or imagery and unwelcome sexual attention or
26
+ advances
27
+ * Trolling, insulting/derogatory comments, and personal or political attacks
28
+ * Public or private harassment
29
+ * Publishing others' private information, such as a physical or electronic
30
+ address, without explicit permission
31
+ * Other conduct which could reasonably be considered inappropriate in a
32
+ professional setting
33
+
34
+ ## Our Responsibilities
35
+
36
+ Project maintainers are responsible for clarifying the standards of acceptable
37
+ behaviour and are expected to take appropriate and fair corrective action in
38
+ response to any instances of unacceptable behaviour.
39
+
40
+ Project maintainers have the right and responsibility to remove, edit, or
41
+ reject comments, commits, code, wiki edits, issues, and other contributions
42
+ that are not aligned to this Code of Conduct, or to ban temporarily or
43
+ permanently any contributor for other behaviours that they deem inappropriate,
44
+ threatening, offensive, or harmful.
45
+
46
+ ## Scope
47
+
48
+ This Code of Conduct applies both within project spaces and in public spaces
49
+ when an individual is representing the project or its community. Examples of
50
+ representing a project or community include using an official project e-mail
51
+ address, posting via an official social media account or acting as an appointed
52
+ representative at an online or offline event. Representation of a project may be
53
+ further defined and clarified by project maintainers.
54
+
55
+ ## Enforcement
56
+
57
+ Instances of abusive, harassing or otherwise unacceptable behaviour may be
58
+ reported by contacting the project team at stefanozoni1@gmail.com. All
59
+ complaints will be reviewed and investigated and will result in a response that
60
+ is deemed necessary and appropriate to the circumstances. The project team is
61
+ obligated to maintain confidentiality concerning the reporter of an incident.
62
+ Further details of specific enforcement policies may be posted separately.
63
+
64
+ Project maintainers who do not follow or enforce the Code of Conduct in good
65
+ faith may face temporary or permanent repercussions as determined by other
66
+ members of the project's leadership.
67
+
68
+ ## Attribution
69
+
70
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71
+ available at <https://www.contributor-covenant.org/version/1/4/code-of-conduct.html>
72
+
73
+ [homepage]: https://www.contributor-covenant.org
74
+
75
+ For answers to common questions about this code of conduct, see
76
+ <https://www.contributor-covenant.org/faq>
@@ -0,0 +1,23 @@
1
+ # **Contributing**
2
+
3
+ When contributing to this repository, please first discuss the change you wish to make via issue,
4
+ email, or any other method with the owners of this repository before making a change.
5
+
6
+ Please note we have a [code of conduct](CODE_OF_CONDUCT.md); please follow it in all your interactions with the project.
7
+
8
+ ## Pull Request Process
9
+
10
+ 1. Ensure any install or build dependencies are removed before the end of the layer when doing a
11
+ build.
12
+ 2. Update the README.md with details of changes to the interface; this includes new environment variables, exposed ports, valid file locations and container parameters.
13
+ 3. Increase the version numbers in any examples files and the README.md to the new version that this
14
+ Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).
15
+ 4. You may merge the Pull Request once you have the sign-off of two other developers, or if you
16
+ do not have permission to do that, you may request the second reviewer to merge it for you.
17
+
18
+ ## Issue Report Process
19
+
20
+ 1. Go to the project's issues.
21
+ 2. Select the template that better fits your issue.
22
+ 3. Read the instructions carefully and write within the template guidelines.
23
+ 4. Submit it and wait for support.
@@ -0,0 +1 @@
1
+ # add your own funding links
@@ -0,0 +1,79 @@
1
+ ---
2
+ name: "🐞 Bug Report"
3
+ about: "Report an issue to help the project improve."
4
+ title: "[Bug] "
5
+ labels: "Type: Bug"
6
+ assignees:
7
+
8
+ ---
9
+
10
+ # **🐞 Bug Report**
11
+
12
+ ## **Describe the bug**
13
+ <!-- A clear and concise description of what the bug is. -->
14
+
15
+ *
16
+
17
+ ---
18
+
19
+ ### **Is this a regression?**
20
+ <!-- Did this behaviour used to work in the previous version? -->
21
+ <!-- Yes, the last version in which this bug was not present was: ... -->
22
+
23
+ ---
24
+
25
+ ### **To Reproduce**
26
+
27
+ <!-- Steps to reproduce the error:
28
+ (e.g.:)
29
+ 1. Use x argument / navigate to
30
+ 2. Fill this information
31
+ 3. Go to...
32
+ 4. See error -->
33
+
34
+ <!-- Write the steps here (add or remove as many steps as needed)-->
35
+
36
+ 1.
37
+ 2.
38
+ 3.
39
+ 4.
40
+
41
+ ---
42
+
43
+ ### **Expected behaviour**
44
+ <!-- A clear and concise description of what you expected to happen. -->
45
+
46
+ *
47
+
48
+ ---
49
+
50
+ ### **Media prove**
51
+ <!-- If applicable, add screenshots or videos to help explain your problem. -->
52
+
53
+ ---
54
+
55
+ ### **Your environment**
56
+
57
+ <!-- use all the applicable bulleted list elements for this specific issue,
58
+ and remove all the bulleted list elements that are not relevant for this issue. -->
59
+
60
+ * OS: <!--[e.g. Ubuntu 5.4.0-26-generic x86_64 / Windows 1904 ...]-->
61
+ * Node version:
62
+ * Npm version:
63
+ * Browser name and version:
64
+
65
+ ---
66
+
67
+ ### **Additional context**
68
+ <!-- Add any other context or additional information about the problem here.-->
69
+
70
+ *
71
+
72
+ <!--📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛
73
+
74
+ Oh, hi there! 😄
75
+
76
+ To expedite issue processing, please search open and closed issues before submitting a new one.
77
+ Please read our Rules of Conduct at this repository's `.github/CODE_OF_CONDUCT.md`
78
+
79
+ 📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛-->
@@ -0,0 +1,41 @@
1
+ ---
2
+ name: "💉 Failing Test"
3
+ about: "Report failing tests or CI jobs."
4
+ title: "[Test] "
5
+ labels: "Type: Test"
6
+ assignees:
7
+
8
+ ---
9
+
10
+ # **💉 Failing Test**
11
+
12
+ ## **Which jobs/test(s) are failing**
13
+ <!-- The CI jobs or tests that are failing -->
14
+
15
+ *
16
+
17
+ ---
18
+
19
+ ## **Reason for failure/description**
20
+ <!-- Try to describe why the test is failing or what we are missing to make it pass. -->
21
+
22
+ ---
23
+
24
+ ### **Media prove**
25
+ <!-- If applicable, add screenshots or videos to help explain your problem. -->
26
+
27
+ ---
28
+
29
+ ### **Additional context**
30
+ <!-- Add any other context or additional information about the problem here. -->
31
+
32
+ *
33
+
34
+ <!--📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛
35
+
36
+ Oh, hi there! 😄
37
+
38
+ To expedite issue processing, please search open and closed issues before submitting a new one.
39
+ Please read our Rules of Conduct at this repository's `.github/CODE_OF_CONDUCT.md`
40
+
41
+ 📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛-->
@@ -0,0 +1,60 @@
1
+ ---
2
+ name: "📚 Documentation or README.md issue report"
3
+ about: "Report an issue in the project's documentation or README.md file."
4
+ title: ""
5
+ labels: "Documentation"
6
+ assignees:
7
+
8
+ ---
9
+ # **📚 Documentation Issue Report**
10
+
11
+ ## **Describe the bug**
12
+ <!-- A clear and concise description of what the bug is. -->
13
+
14
+ *
15
+
16
+ ---
17
+
18
+ ### **To Reproduce**
19
+
20
+ <!-- Steps to reproduce the error:
21
+ (e.g.:)
22
+ 1. Use x argument / navigate to
23
+ 2. Fill this information
24
+ 3. Go to...
25
+ 4. See error -->
26
+
27
+ <!-- Write the steps here (add or remove as many steps as needed)-->
28
+
29
+ 1.
30
+ 2.
31
+ 3.
32
+ 4.
33
+
34
+ ---
35
+
36
+ ### **Media prove**
37
+ <!-- If applicable, add screenshots or videos to help explain your problem. -->
38
+
39
+ ---
40
+
41
+ ## **Describe the solution you'd like**
42
+ <!-- A clear and concise description of what you want to happen. -->
43
+
44
+ *
45
+
46
+ ---
47
+
48
+ ### **Additional context**
49
+ <!-- Add any other context or additional information about the problem here.-->
50
+
51
+ *
52
+
53
+ <!--📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛
54
+
55
+ Oh, hi there! 😄
56
+
57
+ To expedite issue processing, please search open and closed issues before submitting a new one.
58
+ Please read our Rules of Conduct at this repository's `.github/CODE_OF_CONDUCT.md`
59
+
60
+ 📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛-->
@@ -0,0 +1,45 @@
1
+ ---
2
+ name: "🚀🆕 Feature Request"
3
+ about: "Suggest an idea or possible new feature for this project."
4
+ title: ""
5
+ labels: "Type: Feature"
6
+ assignees:
7
+
8
+ ---
9
+
10
+ # **🚀 Feature Request**
11
+
12
+ ## **Is your feature request related to a problem? Please describe.**
13
+ <!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
14
+
15
+ *
16
+
17
+ ---
18
+
19
+ ## **Describe the solution you'd like**
20
+ <!-- A clear and concise description of what you want to happen. -->
21
+
22
+ *
23
+
24
+ ---
25
+
26
+ ## **Describe alternatives you've considered**
27
+ <!-- A clear and concise description of any alternative solutions or features you've considered. -->
28
+
29
+ *
30
+
31
+ ---
32
+
33
+ ### **Additional context**
34
+ <!-- Add any other context or additional information about the problem here.-->
35
+
36
+ *
37
+
38
+ <!--📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛
39
+
40
+ Oh, hi there! 😄
41
+
42
+ To expedite issue processing, please search open and closed issues before submitting a new one.
43
+ Please read our Rules of Conduct at this repository's `.github/CODE_OF_CONDUCT.md`
44
+
45
+ 📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛-->
@@ -0,0 +1,45 @@
1
+ ---
2
+ name: "🚀➕ Enhancement Request"
3
+ about: "Suggest an enhancement for this project. Improve an existing feature"
4
+ title: ""
5
+ labels: "Type: Enhancement"
6
+ assignees:
7
+
8
+ ---
9
+
10
+ # **🚀 Enhancement Request**
11
+
12
+ ## **Is your enhancement request related to a problem? Please describe.**
13
+ <!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
14
+
15
+ *
16
+
17
+ ---
18
+
19
+ ## **Describe the solution you'd like**
20
+ <!-- A clear and concise description of what you want to happen. -->
21
+
22
+ *
23
+
24
+ ---
25
+
26
+ ## **Describe alternatives you've considered**
27
+ <!-- A clear and concise description of any alternative solutions or features you've considered. -->
28
+
29
+ *
30
+
31
+ ---
32
+
33
+ ### **Additional context**
34
+ <!-- Add any other context or additional information about the problem here.-->
35
+
36
+ *
37
+
38
+ <!--📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛
39
+
40
+ Oh, hi there! 😄
41
+
42
+ To expedite issue processing, please search open and closed issues before submitting a new one.
43
+ Please read our Rules of Conduct at this repository's `.github/CODE_OF_CONDUCT.md`
44
+
45
+ 📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛-->
@@ -0,0 +1,100 @@
1
+ ---
2
+ name: "⚠️ Security Report"
3
+ about: "Report an issue to help the project improve."
4
+ title: ""
5
+ labels: "Type: Security"
6
+ assignees:
7
+
8
+ ---
9
+
10
+ <!--📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛
11
+
12
+ Oh, hi there! 😄
13
+
14
+ To expedite issue processing, please search open and closed issues before submitting a new one.
15
+ Please read our Rules of Conduct at this repository's `.github/CODE_OF_CONDUCT.md`
16
+
17
+ FIRST OF ALL, read this project's SECURITY.md file. Located in `.github/SECURITY.md`.
18
+
19
+ READ CAREFULLY IF YOUR ISSUE REPORT CONTAINS SENSIBLE OR PRIVATE DATA:
20
+ (data that might be leaked or subtracted from our servers due to this
21
+ security issue).
22
+
23
+ If this security report (or the guide on how to "identify the security bug") includes
24
+ certain personal information or involves personal identifiable data, or you believe
25
+ that the data that you might leak by exposing the way on how to attack the project
26
+ could be considered as a data leak or could violate the privacy of any kind of
27
+ data or sensible data, please do not post it here and directly email the developer:
28
+ (stefanozoni1@gmail.com). You should post the issue with the least amount of
29
+ sensible or private data as possible to help us manage the security issue, and
30
+ with the extra data sent from your email to the developer (if any), we will deeply
31
+ analyze and try to fix it as fast as possible.
32
+
33
+ If you are in doubt about the data that you might post here (screenshots or media
34
+ also, count as data), please directly email us.
35
+
36
+ The data that must NOT be posted here:
37
+
38
+ * Legal and/or full names
39
+ * Names or usernames combined with other identifiers like phone numbers or email addresses
40
+ * Health or financial information (including insurance information, social security numbers, etc.)
41
+ * Information about political or religious affiliations
42
+ * Information about race, ethnicity, sexual orientation, gender, or other identifying information that could be used for discriminatory purposes
43
+
44
+ 📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛-->
45
+
46
+ # **⚠️ Security Report**
47
+
48
+ ## **Describe the security issue**
49
+ <!-- A clear and concise description of what the bug is. -->
50
+
51
+ *
52
+
53
+ ---
54
+
55
+ ### **To Reproduce**
56
+
57
+ <!-- Steps to reproduce the error:
58
+ (e.g.:)
59
+ 1. Use x argument / navigate to
60
+ 2. Fill this information
61
+ 3. Go to...
62
+ 4. See error -->
63
+
64
+ <!-- Write the steps here (add or remove as many steps as needed)-->
65
+
66
+ 1.
67
+ 2.
68
+ 3.
69
+ 4.
70
+
71
+ ---
72
+
73
+ ### **Expected behaviour**
74
+ <!-- A clear and concise description of what you expected to happen. -->
75
+
76
+ *
77
+
78
+ ---
79
+
80
+ ### **Media prove**
81
+ <!-- If applicable, add screenshots or videos to help explain your problem. -->
82
+
83
+ ---
84
+
85
+ ### **Your environment**
86
+
87
+ <!-- use all the applicable bulleted list elements for this specific issue,
88
+ and remove all the bulleted list elements that are not relevant for this issue. -->
89
+
90
+ * OS: <!--[e.g. Ubuntu 5.4.0-26-generic x86_64 / Windows 1904 ...]-->
91
+ * Node version:
92
+ * Npm version:
93
+ * Browser name and version:
94
+
95
+ ---
96
+
97
+ ### **Additional context**
98
+ <!-- Add any other context or additional information about the problem here.-->
99
+
100
+ *
@@ -0,0 +1,28 @@
1
+ ---
2
+ name: "❓ Question or Support Request"
3
+ about: "Questions and requests for support."
4
+ title: ""
5
+ labels: "Type: Question"
6
+ assignees:
7
+
8
+ ---
9
+
10
+ # **❓ Question or Support Request**
11
+
12
+ ## **Describe your question or ask for support.**
13
+ <!-- A clear and concise description of what your doubt is. -->
14
+
15
+ *
16
+
17
+ <!--📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛
18
+
19
+ Oh, hi there! 😄
20
+
21
+ Before posting any questions or asking for support, first read the project's README.md file and
22
+ (if there is any) the WIKI pages or any other additional documentation that might be listed
23
+ in the project's README.md file.
24
+
25
+ To expedite issue processing, please search open and closed issues before submitting a new one.
26
+ Please read our Rules of Conduct at this repository's `.github/CODE_OF_CONDUCT.md`
27
+
28
+ 📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛-->
@@ -0,0 +1,5 @@
1
+ blank_issues_enabled: true
2
+ contact_links:
3
+ - name: Send an e-mail to the developer
4
+ url: mailto:stefanozoni1@gmail.com
5
+ about: Please do NOT use this email to post issues or feature requests (only important business/personal contact).
@@ -0,0 +1,41 @@
1
+ <!--📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛
2
+
3
+ Oh, hi there! 😄
4
+
5
+ To make our work more accessible, we recommend you to choose any of our available issue templates rather than using (this) a blank template.
6
+
7
+ To expedite issue processing, please search open and closed issues before submitting a new one.
8
+ Please read our Rules of Conduct at this repository's `.github/CODE_OF_CONDUCT.md`
9
+
10
+ 📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛-->
11
+
12
+ # **Blank Issue Report**
13
+
14
+ ## **Describe the issue**
15
+ <!-- A clear and concise description of the problem. -->
16
+
17
+ *
18
+
19
+ ---
20
+
21
+ ### **Media prove**
22
+ <!-- If applicable, add screenshots or videos to help explain your problem. -->
23
+
24
+ ---
25
+
26
+ ### **Your environment**
27
+
28
+ <!-- use all the applicable bulleted list elements for this specific issue,
29
+ and remove all the bulleted list elements that are not relevant for this issue. -->
30
+
31
+ * OS: <!--[e.g. Ubuntu 5.4.0-26-generic x86_64 / Windows 1904 ...]-->
32
+ * Node version:
33
+ * Npm version:
34
+ * Browser name and version:
35
+
36
+ ---
37
+
38
+ ### **Additional context**
39
+ <!-- Add any other context or additional information about the issue here.-->
40
+
41
+ *
@@ -0,0 +1,11 @@
1
+ # **Reporting Security Issues**
2
+
3
+ The project's team and community take security issues.
4
+
5
+ We appreciate your efforts to disclose your findings responsibly and will make every effort to acknowledge your contributions.
6
+
7
+ To report a security issue, go to the project's issues and create a new issue using the ⚠️ Security Report 'issue template'.
8
+
9
+ Read the instructions of this issue template carefully, and if your report could leak data or might expose how to gain access to a restricted area or break the system, please email [stefanozoni1@gmail.com](mailto:stefanozoni1@gmail.com) and include the word "SECURITY" in the subject line.
10
+
11
+ We'll endeavour to respond quickly and keep you updated throughout the process.
@@ -0,0 +1,11 @@
1
+ # **Support**
2
+
3
+ ## Obtain direct support from the project's owners
4
+
5
+ 1. Open a new issue and select the issue with the template called "❓ Question or Support Request".
6
+ 2. Read the instructions carefully in that template and submit the issue asking for support
7
+ or any question.
8
+
9
+ ## Bug reports
10
+
11
+ See the [contributing guidelines](CONTRIBUTING.md) for sharing bug reports and read our [code of conduct](CODE_OF_CONDUCT.md).
@@ -0,0 +1,20 @@
1
+ # Configuration for new-issue-welcome - https://github.com/behaviorbot/new-issue-welcome
2
+
3
+ # Comment to be posted to on first time issues
4
+ newIssueWelcomeComment: >
5
+ Thanks for opening your first issue in /saas_auth! Be sure to follow the issue template and provide every bit of information to help the developers!
6
+
7
+ # Configuration for new-pr-welcome - https://github.com/behaviorbot/new-pr-welcome
8
+
9
+ # Comment to be posted to on PRs from first time contributors in your repository
10
+ newPRWelcomeComment: >
11
+ Thanks for opening this pull request! Please check out our contributing guidelines and make sure to follow the pull request template.
12
+
13
+ # Configuration for first-pr-merge - https://github.com/behaviorbot/first-pr-merge
14
+
15
+ # Comment to be posted to on pull requests merged by a first time user
16
+ firstPRMergeComment: >
17
+ Congrats on merging your first pull request! Keep making great things with us, thanks!!
18
+
19
+ todo:
20
+ keyword: '@todo'
@@ -0,0 +1,30 @@
1
+ version: 2
2
+ updates:
3
+ # GitHub Actions
4
+ - package-ecosystem: github-actions
5
+ directory: /
6
+ schedule:
7
+ interval: daily
8
+ commit-message:
9
+ prefix: "ci(github-actions):"
10
+ # Python
11
+ - package-ecosystem: pip
12
+ directory: /
13
+ schedule:
14
+ interval: daily
15
+ commit-message:
16
+ prefix: "build(pip):"
17
+ # npm
18
+ - package-ecosystem: npm
19
+ directory: /
20
+ schedule:
21
+ interval: daily
22
+ commit-message:
23
+ prefix: "build(npm):"
24
+ # Docker
25
+ - package-ecosystem: docker
26
+ directory: /
27
+ schedule:
28
+ interval: weekly
29
+ commit-message:
30
+ prefix: "build(docker):"