Skip to content

Commit 6e68167

Browse files
authored
security: setup security policy (#1459)
## 📜 Description Added `SECURITY.MD` file. ## 💡 Motivation and Context In the era of AI and upcoming security models from Anthropic/OpenAI I think it's important to define security policy for this repo. We'll prompt to report vulnerability first before public disclosure. ## 📢 Changelog <!-- High level overview of important changes --> <!-- For example: fixed status bar manipulation; added new types declarations; --> <!-- If your changes don't affect one of platform/language below - then remove this platform/language --> ### Docs - added `SECURITY.MD` file; ## 🤔 How Has This Been Tested? Tested via preview. Can be fully tested after a merge 🤞 ## 📸 Screenshots (if appropriate): <img width="1042" height="997" alt="Screenshot 2026-05-12 at 18 28 08" src="https://github.com/user-attachments/assets/3f82055c-0649-4346-98d0-c1f9f4b2e423" /> ## 📝 Checklist - [x] CI successfully passed - [x] I added new mocks and corresponding unit-tests if library API was changed
1 parent a095aa3 commit 6e68167

1 file changed

Lines changed: 37 additions & 0 deletions

File tree

SECURITY.md

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
# Security Policy
2+
3+
## Supported Versions
4+
5+
Only the latest minor release of `react-native-keyboard-controller` receives security fixes. Older versions will not be patched — please upgrade to the latest release before reporting.
6+
7+
## Reporting a Vulnerability
8+
9+
Please **do not** open a public GitHub issue, discussion, or pull request for security problems.
10+
11+
Instead, report vulnerabilities privately through GitHub's [Private Vulnerability Reporting](https://github.com/kirillzyusko/react-native-keyboard-controller/security/advisories/new). This keeps the report confidential until a fix is available and credits you in the resulting advisory.
12+
13+
When reporting, please include:
14+
15+
- A description of the issue and its impact
16+
- Steps to reproduce (minimal repro, affected platform — iOS / Android / Web)
17+
- Affected version(s)
18+
- Any suggested mitigation, if known
19+
20+
## Response Process
21+
22+
- **Acknowledgement:** within 48 hours of report
23+
- **Initial assessment:** within 7 days
24+
- **Fix target:** within 90 days for confirmed vulnerabilities, sooner for high-severity issues
25+
- **Disclosure:** coordinated via a GitHub Security Advisory once a patched release is available
26+
27+
## Scope
28+
29+
In scope:
30+
31+
- The library source under `src/`, `android/`, `ios/`, and the published npm package
32+
33+
Out of scope:
34+
35+
- The example applications (`example/`, `FabricExample/`) — these exist only for local development and integration testing
36+
- Issues in third-party dependencies (please report those upstream)
37+
- Vulnerabilities requiring a physically compromised device or a modified host application

0 commit comments

Comments
 (0)