gaspersic/freeCodeCamp
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

chore(i18n,docs): processed translations (#44571)

Browse Source
This commit is contained in:
camperbot
2021-12-23 18:41:58 +05:30
committed by GitHub
parent 2890970937
commit 8584dfab1d
18 changed files with 234 additions and 90 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
docs/i18n/chinese/_sidebar.md
View File

@ -1,6 +1,7 @@
- **准备开始**
- [介绍](index.md "为 freeCodeCamp.org 社区贡献")
- [常见问题](FAQ.md)
- [Reporting a Vulnerability](security.md)
- **Translation Contribution**
- [Work on translating resources](how-to-translate-files.md)
- [Work on proofreading translations](how-to-proofread-files.md)

4
docs/i18n/chinese/security-hall-of-fame.md
View File

@ -1,6 +1,6 @@
# Responsible Disclosure - Hall of Fame
We appreciate any responsible disclosure of vulnerabilities that might impact the integrity of our platforms and users.
We appreciate any responsible disclosure of vulnerabilities that might impact the integrity of our platforms and users. If you are interested in contributing to the security of our platform, please read our [security policy outlined here](https://contribute.freecodecamp.org/#/security).
While we do not offer any bounties or swags at the moment, we are grateful to these awesome people for helping us keep the platform safe for everyone:
@ -8,5 +8,3 @@ While we do not offer any bounties or swags at the moment, we are grateful to th
- Peter Samir https://www.linkedin.com/in/peter-samir/
> ### Thank you for your contributions :pray:
If you are interested in contributing to the security of our platform, please read our [security policy outlined here](https://contribute.freecodecamp.org/#/security).

47
docs/i18n/chinese/security.md
View File

@ -1,21 +1,46 @@
# Security Policy
This document outlines our security policy for the codebase, and how to report vulnerabilities.
## Versions
| Version | Branch | Supported | Website active |
| ----------- | -------------- | -------------------- | ---------------- |
| production | `prod-current` | :white_check_mark: | freecodecamp.org |
| beta | `prod-staging` | :white_check_mark: | freecodecamp.dev |
| development | `main` | | |
This document outlines our security policy for the codebases, platforms that we operate, and how to report vulnerabilities.
## Reporting a Vulnerability
If you think you have found a vulnerability, _please report responsibly_. Don't create GitHub issues for security issues. Instead, please send an email to `security@freecodecamp.org` and we'll look into it immediately.
Ensure that you are using the **latest**, **stable** and **updated** version of the Operating System and Web Browser available to you on your machine.
We appreciate any responsible disclosure of vulnerabilities that might impact the integrity of our platforms and users.
While we do not offer any bounties or swags at the moment, we'll be happy to list your name in our [Hall of Fame](https://contribute.freecodecamp.org/#/security-hall-of-fame) list, provided the reports are not low-effort for example: using tools & online utilities to report SFP configurations, or SSL Server tests, etc. We consider those in the category of ["beg bounties"](https://www.troyhunt.com/beg-bounties/).
Once you report a vulnerability, we will look into it and make sure that it is not a false positive. We will get back to you if we need to clarify any details. You can submit separate reports for each issue you find.
Ensure that you are using the **latest**, **stable** and **updated** version of the Operating System and Web Browser available to you on your machine.
While we do not offer any bounties or swags at the moment, we'll be happy to list your name in our [Hall of Fame](https://contribute.freecodecamp.org/#/security-hall-of-fame) list, provided the reports are not low-effort.
We consider using tools & online utilities to report issues with SPF & DKIM configs, or SSL Server tests, etc. in the category of ["beg bounties"](https://www.troyhunt.com/beg-bounties/) and are unable to respond to these reports.
## Platforms & Codebases
Here is a list of the platforms and codebases we are accepting reports for:
### Learn Platform
| Version | Branch | Supported | Website active |
| ----------- | -------------- | --------- | ------------------------ |
| production | `prod-current` | Yes | `freecodecamp.org/learn` |
| staging | `prod-staging` | Yes | `freecodecamp.dev/learn` |
| development | `main` | No | |
### Publication Platform
| Version | Supported | Website active |
| ---------- | --------- | ---------------------------------------- |
| production | Yes | `freecodecamp.org/news` |
| localized | Yes | `freecodecamp.org/<language>/news` |
### Mobile app
| Version | Supported | Website active |
| ---------- | --------- | ---------------------------------------------------------------- |
| production | Yes | `https://play.google.com/store/apps/details?id=org.freecodecamp` |
Apart from the above, we are also accepting reports for repositories hosted on GitHub, under the freeCodeCamp organization.
We self-host some of our platforms using open-source software like Ghost & Discourse. If you are reporting a vulnerability please ensure that it is not a bug in the upstream software.

1
docs/i18n/espanol/_sidebar.md
View File

@ -1,6 +1,7 @@
- **Comenzando**
- [Introducción](index.md "Contribuye a la comunidad freeCodeCamp.org")
- [Preguntas más frecuentes](FAQ.md)
- [Reporting a Vulnerability](security.md)
- **Translation Contribution**
- [Work on translating resources](how-to-translate-files.md)
- [Work on proofreading translations](how-to-proofread-files.md)

4
docs/i18n/espanol/security-hall-of-fame.md
View File

@ -1,6 +1,6 @@
# Responsible Disclosure - Hall of Fame
We appreciate any responsible disclosure of vulnerabilities that might impact the integrity of our platforms and users.
We appreciate any responsible disclosure of vulnerabilities that might impact the integrity of our platforms and users. If you are interested in contributing to the security of our platform, please read our [security policy outlined here](https://contribute.freecodecamp.org/#/security).
While we do not offer any bounties or swags at the moment, we are grateful to these awesome people for helping us keep the platform safe for everyone:
@ -8,5 +8,3 @@ While we do not offer any bounties or swags at the moment, we are grateful to th
- Peter Samir https://www.linkedin.com/in/peter-samir/
> ### Thank you for your contributions :pray:
If you are interested in contributing to the security of our platform, please read our [security policy outlined here](https://contribute.freecodecamp.org/#/security).

47
docs/i18n/espanol/security.md
View File

@ -1,21 +1,46 @@
# Security Policy
This document outlines our security policy for the codebase, and how to report vulnerabilities.
## Versions
| Version | Branch | Supported | Website active |
| ----------- | -------------- | -------------------- | ---------------- |
| production | `prod-current` | :white_check_mark: | freecodecamp.org |
| beta | `prod-staging` | :white_check_mark: | freecodecamp.dev |
| development | `main` | | |
This document outlines our security policy for the codebases, platforms that we operate, and how to report vulnerabilities.
## Reporting a Vulnerability
If you think you have found a vulnerability, _please report responsibly_. Don't create GitHub issues for security issues. Instead, please send an email to `security@freecodecamp.org` and we'll look into it immediately.
Ensure that you are using the **latest**, **stable** and **updated** version of the Operating System and Web Browser available to you on your machine.
We appreciate any responsible disclosure of vulnerabilities that might impact the integrity of our platforms and users.
While we do not offer any bounties or swags at the moment, we'll be happy to list your name in our [Hall of Fame](https://contribute.freecodecamp.org/#/security-hall-of-fame) list, provided the reports are not low-effort for example: using tools & online utilities to report SFP configurations, or SSL Server tests, etc. We consider those in the category of ["beg bounties"](https://www.troyhunt.com/beg-bounties/).
Once you report a vulnerability, we will look into it and make sure that it is not a false positive. We will get back to you if we need to clarify any details. You can submit separate reports for each issue you find.
Ensure that you are using the **latest**, **stable** and **updated** version of the Operating System and Web Browser available to you on your machine.
While we do not offer any bounties or swags at the moment, we'll be happy to list your name in our [Hall of Fame](https://contribute.freecodecamp.org/#/security-hall-of-fame) list, provided the reports are not low-effort.
We consider using tools & online utilities to report issues with SPF & DKIM configs, or SSL Server tests, etc. in the category of ["beg bounties"](https://www.troyhunt.com/beg-bounties/) and are unable to respond to these reports.
## Platforms & Codebases
Here is a list of the platforms and codebases we are accepting reports for:
### Learn Platform
| Version | Branch | Supported | Website active |
| ----------- | -------------- | --------- | ------------------------ |
| production | `prod-current` | Yes | `freecodecamp.org/learn` |
| staging | `prod-staging` | Yes | `freecodecamp.dev/learn` |
| development | `main` | No | |
### Publication Platform
| Version | Supported | Website active |
| ---------- | --------- | ---------------------------------------- |
| production | Yes | `freecodecamp.org/news` |
| localized | Yes | `freecodecamp.org/<language>/news` |
### Mobile app
| Version | Supported | Website active |
| ---------- | --------- | ---------------------------------------------------------------- |
| production | Yes | `https://play.google.com/store/apps/details?id=org.freecodecamp` |
Apart from the above, we are also accepting reports for repositories hosted on GitHub, under the freeCodeCamp organization.
We self-host some of our platforms using open-source software like Ghost & Discourse. If you are reporting a vulnerability please ensure that it is not a bug in the upstream software.

1
docs/i18n/italian/_sidebar.md
View File

@ -1,6 +1,7 @@
- **Per iniziare**
- [Introduzione](index.md "Contribuire alla comunità freeCodeCamp.org")
- [Domande frequenti](FAQ.md)
- [Reporting a Vulnerability](security.md)
- **Contribuire alla traduzione**
- [Lavorare a tradurre le risorse](how-to-translate-files.md)
- [Lavorare a correggere le risorse](how-to-proofread-files.md)

4
docs/i18n/italian/security-hall-of-fame.md
View File

@ -1,6 +1,6 @@
# Responsible Disclosure - Hall of Fame
We appreciate any responsible disclosure of vulnerabilities that might impact the integrity of our platforms and users.
We appreciate any responsible disclosure of vulnerabilities that might impact the integrity of our platforms and users. If you are interested in contributing to the security of our platform, please read our [security policy outlined here](https://contribute.freecodecamp.org/#/security).
While we do not offer any bounties or swags at the moment, we are grateful to these awesome people for helping us keep the platform safe for everyone:
@ -8,5 +8,3 @@ While we do not offer any bounties or swags at the moment, we are grateful to th
- Peter Samir https://www.linkedin.com/in/peter-samir/
> ### Thank you for your contributions :pray:
If you are interested in contributing to the security of our platform, please read our [security policy outlined here](https://contribute.freecodecamp.org/#/security).

47
docs/i18n/italian/security.md
View File

@ -1,21 +1,46 @@
# Security Policy
This document outlines our security policy for the codebase, and how to report vulnerabilities.
## Versions
| Version | Branch | Supported | Website active |
| ----------- | -------------- | -------------------- | ---------------- |
| production | `prod-current` | :white_check_mark: | freecodecamp.org |
| beta | `prod-staging` | :white_check_mark: | freecodecamp.dev |
| development | `main` | | |
This document outlines our security policy for the codebases, platforms that we operate, and how to report vulnerabilities.
## Reporting a Vulnerability
If you think you have found a vulnerability, _please report responsibly_. Don't create GitHub issues for security issues. Instead, please send an email to `security@freecodecamp.org` and we'll look into it immediately.
Ensure that you are using the **latest**, **stable** and **updated** version of the Operating System and Web Browser available to you on your machine.
We appreciate any responsible disclosure of vulnerabilities that might impact the integrity of our platforms and users.
While we do not offer any bounties or swags at the moment, we'll be happy to list your name in our [Hall of Fame](https://contribute.freecodecamp.org/#/security-hall-of-fame) list, provided the reports are not low-effort for example: using tools & online utilities to report SFP configurations, or SSL Server tests, etc. We consider those in the category of ["beg bounties"](https://www.troyhunt.com/beg-bounties/).
Once you report a vulnerability, we will look into it and make sure that it is not a false positive. We will get back to you if we need to clarify any details. You can submit separate reports for each issue you find.
Ensure that you are using the **latest**, **stable** and **updated** version of the Operating System and Web Browser available to you on your machine.
While we do not offer any bounties or swags at the moment, we'll be happy to list your name in our [Hall of Fame](https://contribute.freecodecamp.org/#/security-hall-of-fame) list, provided the reports are not low-effort.
We consider using tools & online utilities to report issues with SPF & DKIM configs, or SSL Server tests, etc. in the category of ["beg bounties"](https://www.troyhunt.com/beg-bounties/) and are unable to respond to these reports.
## Platforms & Codebases
Here is a list of the platforms and codebases we are accepting reports for:
### Learn Platform
| Version | Branch | Supported | Website active |
| ----------- | -------------- | --------- | ------------------------ |
| production | `prod-current` | Yes | `freecodecamp.org/learn` |
| staging | `prod-staging` | Yes | `freecodecamp.dev/learn` |
| development | `main` | No | |
### Publication Platform
| Version | Supported | Website active |
| ---------- | --------- | ---------------------------------------- |
| production | Yes | `freecodecamp.org/news` |
| localized | Yes | `freecodecamp.org/<language>/news` |
### Mobile app
| Version | Supported | Website active |
| ---------- | --------- | ---------------------------------------------------------------- |
| production | Yes | `https://play.google.com/store/apps/details?id=org.freecodecamp` |
Apart from the above, we are also accepting reports for repositories hosted on GitHub, under the freeCodeCamp organization.
We self-host some of our platforms using open-source software like Ghost & Discourse. If you are reporting a vulnerability please ensure that it is not a bug in the upstream software.

1
docs/i18n/japanese/_sidebar.md
View File

@ -1,6 +1,7 @@
- **はじめに**
- [イントロダクション](index.md "freeCodeCamp.org コミュニティに貢献する")
- [よくある質問](FAQ.md)
- [Reporting a Vulnerability](security.md)
- **翻訳のコントリビューション**
- [リソースを翻訳する](how-to-translate-files.md)
- [翻訳を校正する](how-to-proofread-files.md)

4
docs/i18n/japanese/security-hall-of-fame.md
View File

@ -1,6 +1,6 @@
# Responsible Disclosure - Hall of Fame
We appreciate any responsible disclosure of vulnerabilities that might impact the integrity of our platforms and users.
We appreciate any responsible disclosure of vulnerabilities that might impact the integrity of our platforms and users. If you are interested in contributing to the security of our platform, please read our [security policy outlined here](https://contribute.freecodecamp.org/#/security).
While we do not offer any bounties or swags at the moment, we are grateful to these awesome people for helping us keep the platform safe for everyone:
@ -8,5 +8,3 @@ While we do not offer any bounties or swags at the moment, we are grateful to th
- Peter Samir https://www.linkedin.com/in/peter-samir/
> ### Thank you for your contributions :pray:
If you are interested in contributing to the security of our platform, please read our [security policy outlined here](https://contribute.freecodecamp.org/#/security).

47
docs/i18n/japanese/security.md
View File

@ -1,21 +1,46 @@
# Security Policy
This document outlines our security policy for the codebase, and how to report vulnerabilities.
## Versions
| Version | Branch | Supported | Website active |
| ----------- | -------------- | -------------------- | ---------------- |
| production | `prod-current` | :white_check_mark: | freecodecamp.org |
| beta | `prod-staging` | :white_check_mark: | freecodecamp.dev |
| development | `main` | | |
This document outlines our security policy for the codebases, platforms that we operate, and how to report vulnerabilities.
## Reporting a Vulnerability
If you think you have found a vulnerability, _please report responsibly_. Don't create GitHub issues for security issues. Instead, please send an email to `security@freecodecamp.org` and we'll look into it immediately.
Ensure that you are using the **latest**, **stable** and **updated** version of the Operating System and Web Browser available to you on your machine.
We appreciate any responsible disclosure of vulnerabilities that might impact the integrity of our platforms and users.
While we do not offer any bounties or swags at the moment, we'll be happy to list your name in our [Hall of Fame](https://contribute.freecodecamp.org/#/security-hall-of-fame) list, provided the reports are not low-effort for example: using tools & online utilities to report SFP configurations, or SSL Server tests, etc. We consider those in the category of ["beg bounties"](https://www.troyhunt.com/beg-bounties/).
Once you report a vulnerability, we will look into it and make sure that it is not a false positive. We will get back to you if we need to clarify any details. You can submit separate reports for each issue you find.
Ensure that you are using the **latest**, **stable** and **updated** version of the Operating System and Web Browser available to you on your machine.
While we do not offer any bounties or swags at the moment, we'll be happy to list your name in our [Hall of Fame](https://contribute.freecodecamp.org/#/security-hall-of-fame) list, provided the reports are not low-effort.
We consider using tools & online utilities to report issues with SPF & DKIM configs, or SSL Server tests, etc. in the category of ["beg bounties"](https://www.troyhunt.com/beg-bounties/) and are unable to respond to these reports.
## Platforms & Codebases
Here is a list of the platforms and codebases we are accepting reports for:
### Learn Platform
| Version | Branch | Supported | Website active |
| ----------- | -------------- | --------- | ------------------------ |
| production | `prod-current` | Yes | `freecodecamp.org/learn` |
| staging | `prod-staging` | Yes | `freecodecamp.dev/learn` |
| development | `main` | No | |
### Publication Platform
| Version | Supported | Website active |
| ---------- | --------- | ---------------------------------------- |
| production | Yes | `freecodecamp.org/news` |
| localized | Yes | `freecodecamp.org/<language>/news` |
### Mobile app
| Version | Supported | Website active |
| ---------- | --------- | ---------------------------------------------------------------- |
| production | Yes | `https://play.google.com/store/apps/details?id=org.freecodecamp` |
Apart from the above, we are also accepting reports for repositories hosted on GitHub, under the freeCodeCamp organization.
We self-host some of our platforms using open-source software like Ghost & Discourse. If you are reporting a vulnerability please ensure that it is not a bug in the upstream software.

1
docs/i18n/portuguese/_sidebar.md
View File

@ -1,6 +1,7 @@
- **Primeiros passos**
- [Introdução](index.md "Contribua para a comunidade do freeCodeCamp.org")
- [Perguntas frequentes](FAQ.md)
- [Reporting a Vulnerability](security.md)
- **Contribuição de tradução**
- [Ajude na tradução de recursos](how-to-translate-files.md)
- [Ajude na revisão de traduções](how-to-proofread-files.md)

12
docs/i18n/portuguese/security-hall-of-fame.md
View File

@ -1,12 +1,10 @@
# Responsible Disclosure - Hall of Fame
# Divulgação responsável - Lista dos famosos
We appreciate any responsible disclosure of vulnerabilities that might impact the integrity of our platforms and users.
We appreciate any responsible disclosure of vulnerabilities that might impact the integrity of our platforms and users. If you are interested in contributing to the security of our platform, please read our [security policy outlined here](https://contribute.freecodecamp.org/#/security).
While we do not offer any bounties or swags at the moment, we are grateful to these awesome people for helping us keep the platform safe for everyone:
Embora não possamos oferecer nenhuma recompensa ou troca no momento, agradecemos a essas pessoas incríveis por nos ajudar a manter a plataforma segura para todos:
- Mehul Mohan from [codedamn](https://codedamn.com) ([@mehulmpt](https://twitter.com/mehulmpt)) - [Vulnerability Fix](https://github.com/freeCodeCamp/freeCodeCamp/blob/bb5a9e815313f1f7c91338e171bfe5acb8f3e346/client/src/components/Flash/index.js)
- Mehul Mohan, da [codedamn](https://codedamn.com) ([@mehulmpt](https://twitter.com/mehulmpt)) - [Fix de vulnerabilidade](https://github.com/freeCodeCamp/freeCodeCamp/blob/bb5a9e815313f1f7c91338e171bfe5acb8f3e346/client/src/components/Flash/index.js)
- Peter Samir https://www.linkedin.com/in/peter-samir/
> ### Thank you for your contributions :pray:
If you are interested in contributing to the security of our platform, please read our [security policy outlined here](https://contribute.freecodecamp.org/#/security).
> ### Agradecemos por suas contribuições :pray:

51
docs/i18n/portuguese/security.md
View File

@ -1,21 +1,46 @@
# Security Policy
# Política de segurança
This document outlines our security policy for the codebase, and how to report vulnerabilities.
## Versions
| Version | Branch | Supported | Website active |
| ----------- | -------------- | -------------------- | ---------------- |
| production | `prod-current` | :white_check_mark: | freecodecamp.org |
| beta | `prod-staging` | :white_check_mark: | freecodecamp.dev |
| development | `main` | | |
This document outlines our security policy for the codebases, platforms that we operate, and how to report vulnerabilities.
## Reporting a Vulnerability
If you think you have found a vulnerability, _please report responsibly_. Don't create GitHub issues for security issues. Instead, please send an email to `security@freecodecamp.org` and we'll look into it immediately.
Se você acha que encontrou uma vulnerabilidade, _reporte-a de modo responsável_. Não crie issues no GitHub para problemas de segurança. Em vez disso, envie um e-mail para `security@freecodecamp.org` e investigaremos isso imediatamente.
Ensure that you are using the **latest**, **stable** and **updated** version of the Operating System and Web Browser available to you on your machine.
We appreciate any responsible disclosure of vulnerabilities that might impact the integrity of our platforms and users.
While we do not offer any bounties or swags at the moment, we'll be happy to list your name in our [Hall of Fame](https://contribute.freecodecamp.org/#/security-hall-of-fame) list, provided the reports are not low-effort for example: using tools & online utilities to report SFP configurations, or SSL Server tests, etc. We consider those in the category of ["beg bounties"](https://www.troyhunt.com/beg-bounties/).
Once you report a vulnerability, we will look into it and make sure that it is not a false positive. We will get back to you if we need to clarify any details. You can submit separate reports for each issue you find.
Ensure that you are using the **latest**, **stable** and **updated** version of the Operating System and Web Browser available to you on your machine.
While we do not offer any bounties or swags at the moment, we'll be happy to list your name in our [Hall of Fame](https://contribute.freecodecamp.org/#/security-hall-of-fame) list, provided the reports are not low-effort.
We consider using tools & online utilities to report issues with SPF & DKIM configs, or SSL Server tests, etc. in the category of ["beg bounties"](https://www.troyhunt.com/beg-bounties/) and are unable to respond to these reports.
## Platforms & Codebases
Here is a list of the platforms and codebases we are accepting reports for:
### Learn Platform
| Versão | Branch | Suportado | Site da web ativo |
| --------------- | -------------- | --------- | ------------------------ |
| produção | `prod-current` | Yes | `freecodecamp.org/learn` |
| staging | `prod-staging` | Yes | `freecodecamp.dev/learn` |
| desenvolvimento | `main` | No | |
### Publication Platform
| Version | Supported | Website active |
| ---------- | --------- | ---------------------------------------- |
| production | Yes | `freecodecamp.org/news` |
| localized | Yes | `freecodecamp.org/<language>/news` |
### Mobile app
| Version | Supported | Website active |
| ---------- | --------- | ---------------------------------------------------------------- |
| production | Yes | `https://play.google.com/store/apps/details?id=org.freecodecamp` |
Apart from the above, we are also accepting reports for repositories hosted on GitHub, under the freeCodeCamp organization.
We self-host some of our platforms using open-source software like Ghost & Discourse. If you are reporting a vulnerability please ensure that it is not a bug in the upstream software.

1
docs/i18n/ukrainian/_sidebar.md
View File

@ -1,6 +1,7 @@
- **Початок роботи**
- [Вступ](index.md "Зробіть свій внесок у спільноту freeCodeCamp.org")
- [Поширені питання](FAQ.md)
- [Reporting a Vulnerability](security.md)
- **Внесок у переклад**
- [Робота над перекладом матеріалів](how-to-translate-files.md)
- [Робота над вичиткою перекладів](how-to-proofread-files.md)

4
docs/i18n/ukrainian/security-hall-of-fame.md
View File

@ -1,6 +1,6 @@
# Responsible Disclosure - Hall of Fame
We appreciate any responsible disclosure of vulnerabilities that might impact the integrity of our platforms and users.
We appreciate any responsible disclosure of vulnerabilities that might impact the integrity of our platforms and users. If you are interested in contributing to the security of our platform, please read our [security policy outlined here](https://contribute.freecodecamp.org/#/security).
While we do not offer any bounties or swags at the moment, we are grateful to these awesome people for helping us keep the platform safe for everyone:
@ -8,5 +8,3 @@ While we do not offer any bounties or swags at the moment, we are grateful to th
- Peter Samir https://www.linkedin.com/in/peter-samir/
> ### Thank you for your contributions :pray:
If you are interested in contributing to the security of our platform, please read our [security policy outlined here](https://contribute.freecodecamp.org/#/security).

47
docs/i18n/ukrainian/security.md
View File

@ -1,21 +1,46 @@
# Security Policy
This document outlines our security policy for the codebase, and how to report vulnerabilities.
## Versions
| Version | Branch | Supported | Website active |
| ----------- | -------------- | -------------------- | ---------------- |
| production | `prod-current` | :white_check_mark: | freecodecamp.org |
| beta | `prod-staging` | :white_check_mark: | freecodecamp.dev |
| development | `main` | | |
This document outlines our security policy for the codebases, platforms that we operate, and how to report vulnerabilities.
## Reporting a Vulnerability
If you think you have found a vulnerability, _please report responsibly_. Don't create GitHub issues for security issues. Instead, please send an email to `security@freecodecamp.org` and we'll look into it immediately.
Ensure that you are using the **latest**, **stable** and **updated** version of the Operating System and Web Browser available to you on your machine.
We appreciate any responsible disclosure of vulnerabilities that might impact the integrity of our platforms and users.
While we do not offer any bounties or swags at the moment, we'll be happy to list your name in our [Hall of Fame](https://contribute.freecodecamp.org/#/security-hall-of-fame) list, provided the reports are not low-effort for example: using tools & online utilities to report SFP configurations, or SSL Server tests, etc. We consider those in the category of ["beg bounties"](https://www.troyhunt.com/beg-bounties/).
Once you report a vulnerability, we will look into it and make sure that it is not a false positive. We will get back to you if we need to clarify any details. You can submit separate reports for each issue you find.
Ensure that you are using the **latest**, **stable** and **updated** version of the Operating System and Web Browser available to you on your machine.
While we do not offer any bounties or swags at the moment, we'll be happy to list your name in our [Hall of Fame](https://contribute.freecodecamp.org/#/security-hall-of-fame) list, provided the reports are not low-effort.
We consider using tools & online utilities to report issues with SPF & DKIM configs, or SSL Server tests, etc. in the category of ["beg bounties"](https://www.troyhunt.com/beg-bounties/) and are unable to respond to these reports.
## Platforms & Codebases
Here is a list of the platforms and codebases we are accepting reports for:
### Learn Platform
| Version | Branch | Supported | Website active |
| ----------- | -------------- | --------- | ------------------------ |
| production | `prod-current` | Yes | `freecodecamp.org/learn` |
| staging | `prod-staging` | Yes | `freecodecamp.dev/learn` |
| development | `main` | No | |
### Publication Platform
| Version | Supported | Website active |
| ---------- | --------- | ---------------------------------------- |
| production | Yes | `freecodecamp.org/news` |
| localized | Yes | `freecodecamp.org/<language>/news` |
### Mobile app
| Version | Supported | Website active |
| ---------- | --------- | ---------------------------------------------------------------- |
| production | Yes | `https://play.google.com/store/apps/details?id=org.freecodecamp` |
Apart from the above, we are also accepting reports for repositories hosted on GitHub, under the freeCodeCamp organization.
We self-host some of our platforms using open-source software like Ghost & Discourse. If you are reporting a vulnerability please ensure that it is not a bug in the upstream software.