Skip to content

Commit

Permalink
Merge branch 'next' into feat/add-ability-to-toggle-settings-in-iframe
Browse files Browse the repository at this point in the history
  • Loading branch information
ainouzgali authored Oct 29, 2023
2 parents 4ede565 + ca1176b commit 242fabb
Show file tree
Hide file tree
Showing 149 changed files with 2,262 additions and 1,689 deletions.
5 changes: 4 additions & 1 deletion .cspell.json
Original file line number Diff line number Diff line change
Expand Up @@ -515,7 +515,10 @@
"Kamil",
"Myśliwiec",
"nestframework",
"ryver"
"ryver",
"idempotency",
"IDEMPOTENCY",
"Idempotency"
],
"flagWords": [],
"patterns": [
Expand Down
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ Your contribution, no matter its size, holds immense value. We eagerly await to
·
<a href="https://roadmap.novu.co">Roadmap</a>
·
<a href="https://twitter.com/novuhq">Twitter</a>
<a href="https://twitter.com/novuhq">X</a>
·
<a href="https://notifications.directory">Notifications Directory</a>
</p>
Expand Down Expand Up @@ -141,7 +141,7 @@ await novu.trigger('<TRIGGER_NAME>', {

## Embeddable Notification Center

Using the Novu API and admin panel, you can easily add a real-time notification center to your web app without building it yourself. You can use our React / Vue / Angular component or an iframe embed.
Using the Novu API and admin panel, you can easily add a real-time notification center to your web app without building it yourself. You can use our [React](https://docs.novu.co/notification-center/client/react/get-started) / [Vue](https://docs.novu.co/notification-center/client/vue) / [Angular](https://docs.novu.co/notification-center/client/angular) components or an [iframe embed](https://docs.novu.co/notification-center/client/iframe).

<div align="center">
<img width="762" alt="notification-center-912bb96e009fb3a69bafec23bcde00b0" src="https://user-images.githubusercontent.com/80174214/193887395-f1c95042-b4e6-480e-a89c-a78aa247fa90.gif" alt-text="GIF of Novu's Embeddable Notification Center">
Expand Down
53 changes: 29 additions & 24 deletions SECURITY.md
Original file line number Diff line number Diff line change
@@ -1,14 +1,18 @@
# Security

Contact: [email protected]
**Contact:** [email protected]

Based on [https://supabase.com/.well-known/security.txt](https://supabase.com/.well-known/security.txt)
Safeguarding our Novu systems is a top concern for us. Nevertheless, despite our best efforts to fortify them, vulnerabilities may still be present.

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.
If you come across a vulnerability, please inform us promptly so we can promptly resolve it. We kindly request your assistance in enhancing the security of both our clients and our systems.

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.
## Reporting a Vulnerability

## Out of scope vulnerabilities:
**In Scope Vulnerabilities:**

- Any security issues that might put at risk the confidentiality, integrity, or accessibility of our systems or data.

**Out of Scope Vulnerabilities:**

- Clickjacking on pages with no sensitive actions.

Expand All @@ -18,41 +22,42 @@ In the event that you discover a vulnerability, please let us know so we can add

- 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.
- Content spoofing and text injection issues without showing an attack vector or the ability to modify HTML/CSS.

- Email spoofing
- Email spoofing.

- Missing DNSSEC, CAA, CSP headers
- Missing DNSSEC, CAA, CSP headers.

- Lack of Secure or HTTP only flag on non-sensitive cookies
- Lack of Secure or HTTP-only flags on non-sensitive cookies.

- Deadlinks
- Deadlinks.

## Please do the following:
**Reporting Instructions:**

- E-mail your findings to [[email protected]](mailto:[email protected]).
1. Email your findings to **[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.
2. Automated scanning tools should not be used on our infrastructure or dashboard. If you have a need for this, please reach out to us, and we'll assist you in setting up a secure sandbox environment.

- 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,
3. Please do not exploit the vulnerability or issue you've found, such as downloading excessive data or tampering with others' data.

- Do not reveal the problem to others until it has been resolved,
4. Please keep the issue confidential until we've fixed it.

- Do not use attacks on physical security, social engineering, distributed denial of service, spam or applications of third parties,
5. Do not use attacks on physical security, social engineering, distributed denial of service, spam, or third-party applications.

- 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.
6. Please share enough details for us to understand and fix the issue as fast as we can. Typically, providing the IP address or the URL of the affected system along with a description of the problem should be enough, though more intricate issues might need additional clarification.

## What we promise:
## What *We* Promise

- We will respond to your report within 3 business days with our evaluation of the report and an expected resolution date,
1. We'll get back to you within 3 business days with our assessment of the report and an estimated date when we expect to resolve it.

- If you have followed the instructions above, we will not take any legal action against you in regard to the report,
2. We will not take any legal action against you related to the report, if you have adhered to the reporting instructions above.

- We will handle your report with strict confidentiality, and not pass on your personal details to third parties without your permission,
3. We'll treat your report with utmost confidentiality and won't share your personal information with third parties without your consent.

- We will keep you informed of the progress towards resolving the problem,
4. We'll be keeping you updated of the progress toward fixing the issue.

- In the public information concerning the problem reported, we will give your name as the discoverer of the problem (unless you desire otherwise), and
5. We'll credit you as the discoverer of the issue (unless you request otherwise), in public disclosures of the reported issue.

- 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.
6. We aim to resolve all issues promptly and are eager to actively contribute to the ultimate publication on the problem, once the problem has been resolved.

We truly value your contributions in strengthening our security.
Loading

0 comments on commit 242fabb

Please sign in to comment.