forked from novuhq/novu
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'add-submodules-to-project' into fix-version-with-submod…
…ules
- Loading branch information
Showing
933 changed files
with
23,081 additions
and
17,184 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -13,7 +13,7 @@ jobs: | |
| with: | ||
| repo-token: "${{ secrets.GITHUB_TOKEN }}" | ||
|
|
||
| - uses: microsoft/[email protected].4 | ||
| - uses: microsoft/[email protected].7 | ||
| name: PR Metrics | ||
| env: | ||
| PR_METRICS_ACCESS_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,4 @@ | ||
| FROM gitpod/workspace-mongodb | ||
|
|
||
| RUN sudo apt-get update && sudo apt-get install -y redis-server && sudo rm -rf /var/lib/apt/lists/* | ||
| RUN npm install -g pnpm@7.33.4 | ||
| RUN npm install -g pnpm@8.9.0 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,58 +1,43 @@ | ||
| # Security | ||
| # Security Contact | ||
|
|
||
| Contact: [email protected] | ||
| **Contact:** [email protected] | ||
|
|
||
| Based on [https://supabase.com/.well-known/security.txt](https://supabase.com/.well-known/security.txt) | ||
| At Novu, we prioritize the security of our systems. While we strive to make our systems as secure as possible, vulnerabilities can still exist. If you discover a vulnerability, we kindly request your assistance in helping us enhance our security measures and protect our clients. | ||
|
|
||
| We place a high priority on the security of our systems at Novu. However, no matter how hard we try to make our systems secure, vulnerabilities can still exist. | ||
| ## Reporting a Vulnerability | ||
|
|
||
| In the event that you discover a vulnerability, please let us know so we can address it as soon as possible. We would like to ask you to help us better protect our clients and our systems. | ||
| **In Scope Vulnerabilities:** | ||
|
|
||
| ## Out of scope vulnerabilities: | ||
| - Any security issues that could jeopardize the confidentiality, integrity, or availability of our systems or data. | ||
|
|
||
| - Clickjacking on pages with no sensitive actions. | ||
| **Out of Scope Vulnerabilities:** | ||
|
|
||
| - Clickjacking on pages with no sensitive actions. | ||
| - Unauthenticated/logout/login CSRF. | ||
|
|
||
| - Attacks requiring MITM or physical access to a user's device. | ||
|
|
||
| - Any activity that could lead to the disruption of our service (DoS). | ||
|
|
||
| - Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS. | ||
|
|
||
| - Email spoofing | ||
|
|
||
| - Missing DNSSEC, CAA, CSP headers | ||
|
|
||
| - Lack of Secure or HTTP only flag on non-sensitive cookies | ||
|
|
||
| - Deadlinks | ||
|
|
||
| ## Please do the following: | ||
|
|
||
| - E-mail your findings to [[email protected]](mailto:[email protected]). | ||
|
|
||
| - Do not run automated scanners on our infrastructure or dashboard. If you wish to do this, contact us and we will set up a sandbox for you. | ||
|
|
||
| - Do not take advantage of the vulnerability or problem you have discovered, for example by downloading more data than necessary to demonstrate the vulnerability or deleting or modifying other people's data, | ||
|
|
||
| - Do not reveal the problem to others until it has been resolved, | ||
|
|
||
| - Do not use attacks on physical security, social engineering, distributed denial of service, spam or applications of third parties, | ||
|
|
||
| - Do provide sufficient information to reproduce the problem, so we will be able to resolve it as quickly as possible. Usually, the IP address or the URL of the affected system and a description of the vulnerability will be sufficient, but complex vulnerabilities may require further explanation. | ||
|
|
||
| ## What we promise: | ||
|
|
||
| - We will respond to your report within 3 business days with our evaluation of the report and an expected resolution date, | ||
|
|
||
| - If you have followed the instructions above, we will not take any legal action against you in regard to the report, | ||
|
|
||
| - We will handle your report with strict confidentiality, and not pass on your personal details to third parties without your permission, | ||
|
|
||
| - We will keep you informed of the progress towards resolving the problem, | ||
|
|
||
| - In the public information concerning the problem reported, we will give your name as the discoverer of the problem (unless you desire otherwise), and | ||
|
|
||
| - We strive to resolve all problems as quickly as possible, and we would like to play an active role in the ultimate publication on the problem after it is resolved. | ||
|
|
||
| - Content spoofing and text injection issues without showing an attack vector or the ability to modify HTML/CSS. | ||
| - Email spoofing. | ||
| - Missing DNSSEC, CAA, CSP headers. | ||
| - Lack of Secure or HTTP-only flags on non-sensitive cookies. | ||
| - Deadlinks. | ||
|
|
||
| **Reporting Instructions:** | ||
|
|
||
| 1. Email your findings to **[email protected]**. | ||
| 2. Please refrain from running automated scanners on our infrastructure or dashboard. If you intend to do so, contact us, and we will set up a sandbox for your testing. | ||
| 3. Do not exploit the vulnerability or problem you have discovered, such as downloading more data than necessary or deleting/modifying others' data. | ||
| 4. Keep the problem confidential until it has been resolved. | ||
| 5. Do not use attacks on physical security, social engineering, distributed denial of service, spam, or third-party applications. | ||
| 6. Provide sufficient information to reproduce the problem, including the IP address or URL of the affected system and a clear description of the vulnerability. Complex vulnerabilities may require additional explanation. | ||
|
|
||
| ## What We Promise | ||
|
|
||
| 1. We will respond to your report within 3 business days, providing an evaluation of the report and an expected resolution date. | ||
| 2. If you have adhered to the reporting instructions, we will not take any legal action against you in relation to the report. | ||
| 3. We will maintain strict confidentiality regarding your report and will not share your personal details with third parties without your consent. | ||
| 4. You will be kept informed of the progress toward resolving the problem. | ||
| 5. In public disclosures about the reported problem, we will credit you as the discoverer of the issue (unless you request otherwise). | ||
| 6. We are committed to resolving all issues promptly and actively participating in the public disclosure of the issue once it's resolved. | ||
|
|
||
| Your contribution to enhancing our security is greatly appreciated. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.