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
Copy file name to clipboardExpand all lines: README.md
+23-4Lines changed: 23 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,23 @@
1
1
# ⚛️ React Resize Detector Context
2
2
3
+
3
4

4
5
6
+
7
+
5
8
A lightweight React context that leverages [react-resize-detector](https://github.com/maslianok/react-resize-detector) to dynamically detect the
6
9
current breakpoint based on an element's width. It provides utility functions and helper components to conditionally render content based on
7
10
responsive breakpoints – all fully typed in TypeScript for excellent IDE support. 😎
We release patches for security vulnerabilities. Which versions are eligible for receiving such patches depends on the CVSS v3.0 Rating:
6
+
7
+
| Version | Supported |
8
+
| ------- | ------------------ |
9
+
| 0.1.x |:white_check_mark:|
10
+
| < 0.1.0 |:x:|
11
+
12
+
## Reporting a Vulnerability
13
+
14
+
We take the security of our software seriously. If you believe you have found a security vulnerability in react-resize-detector-context, please report it to us as described below.
15
+
16
+
**Please do not report security vulnerabilities through public GitHub issues.**
You should receive a response within 48 hours. If for some reason you do not, please follow up via email to ensure we received your original message.
21
+
22
+
Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
23
+
24
+
- Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
25
+
- Full paths of source file(s) related to the manifestation of the issue
26
+
- The location of the affected source code (tag/branch/commit or direct URL)
27
+
- Any special configuration required to reproduce the issue
28
+
- Step-by-step instructions to reproduce the issue
29
+
- Proof-of-concept or exploit code (if possible)
30
+
- Impact of the issue, including how an attacker might exploit the issue
31
+
32
+
This information will help us triage your report more quickly.
33
+
34
+
## Preferred Languages
35
+
36
+
We prefer all communications to be in English or German.
37
+
38
+
## Policy
39
+
40
+
We follow the principle of [Responsible Disclosure](https://en.wikipedia.org/wiki/Responsible_disclosure).
41
+
42
+
## Comments on this Policy
43
+
44
+
If you have suggestions on how this process could be improved please submit a pull request.
0 commit comments