You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
6
+
7
+
We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
8
+
9
+
## Our Standards
10
+
11
+
Examples of behavior that contributes to a positive environment for our community include:
12
+
13
+
- Demonstrating empathy and kindness toward other people
14
+
- Being respectful of differing opinions, viewpoints, and experiences
15
+
- Giving and gracefully accepting constructive feedback
16
+
- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
17
+
- Focusing on what is best not just for us as individuals, but for the overall community
18
+
19
+
Examples of unacceptable behavior include:
20
+
21
+
- The use of sexualized language or imagery, and sexual attention or advances of any kind
22
+
- Trolling, insulting or derogatory comments, and personal or political attacks
23
+
- Public or private harassment
24
+
- Publishing others' private information, such as a physical or email address, without their explicit permission
25
+
- Other conduct which could reasonably be considered inappropriate in a professional setting
26
+
27
+
## Enforcement Responsibilities
28
+
29
+
Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
30
+
31
+
Community leaders 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, and will communicate reasons for moderation decisions when appropriate.
32
+
33
+
## Scope
34
+
35
+
This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
36
+
37
+
## Enforcement
38
+
39
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [Clémence Lesné](mailto:clemlesne@users.noreply.github.com). All complaints will be reviewed and investigated promptly and fairly.
40
+
41
+
All community leaders are obligated to respect the privacy and security of the reporter of any incident.
42
+
43
+
## Enforcement Guidelines
44
+
45
+
Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
46
+
47
+
### 1. Correction
48
+
49
+
**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
50
+
51
+
**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
52
+
53
+
### 2. Warning
54
+
55
+
**Community Impact**: A violation through a single incident or series of actions.
56
+
57
+
**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
58
+
59
+
### 3. Temporary Ban
60
+
61
+
**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
62
+
63
+
**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
64
+
65
+
### 4. Permanent Ban
66
+
67
+
**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
68
+
69
+
**Consequence**: A permanent ban from any sort of public interaction within the community.
70
+
71
+
## Attribution
72
+
73
+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
74
+
75
+
Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
76
+
77
+
For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
Copy file name to clipboardExpand all lines: README.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# 🔒 Private GPT
1
+
# Employee communication with Private GPT – AI-powered chatbot you can trust
2
2
3
3
> 👋🏻 Demo available at [private-gpt.shopping-cart-devops-demo.lesne.pro](https://private-gpt.shopping-cart-devops-demo.lesne.pro).
4
4
@@ -153,4 +153,12 @@ sequenceDiagram
153
153
154
154
WIP
155
155
156
+
## [Security](./SECURITY.md)
157
+
158
+
## Support
159
+
160
+
This project is open source and maintained by people like you. If you need help or found a bug, please feel free to open an issue on the [clemlesne/private-gpt](https://github.com/clemlesne/private-gpt) GitHub project.
At each build, a vulnerability scan is performed on the system. If a vulnerability that can be upgraded is detected, the build is stopped and the image is not pushed to the registry. Vulnerability is reported in [GitHub Security](https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning). The maintainers are alterted and have access to reports.
6
+
7
+
Automation is supported by [Snyk](https://snyk.io) and [Semgrep](https://semgrep.dev). Helm chart, configuration files, and containers, are scanned for vulnerabilities and misconfigurations.
8
+
9
+
## Reporting a vulnerability
10
+
11
+
If you think you have found a vulnerability, please do not open an issue on GitHub. Instead, please send an email to [Clémence Lesné](mailto:clemence@lesne.pro).
12
+
13
+
## Chain of trust
14
+
15
+
Helm chart and containers are not signed yet with a GPG key.
16
+
17
+
## Reliability notes
18
+
19
+
Systems are built every days. Each image is accompanied by a SBOM (Software Bill of Materials) which allows to verify that the installed packages are those expected. This speed has the advantage of minimizing exposure to security flaws, which will then be corrected on the build environments in 24 hours.
20
+
21
+
Nevertheless it can happen that a package provider (e.g. Debian, Canonical, Red Hat) deploys a system update that introduces a bug. This is difficult to predict.
0 commit comments