Skip to content

Commit fa5395e

Browse files
authored
Revise SECURITY.md for supported versions and reporting
Updated the security policy to reflect supported versions and reporting methods.
1 parent 6c03c6c commit fa5395e

File tree

1 file changed

+24
-0
lines changed

1 file changed

+24
-0
lines changed

SECURITY.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
# Security Policy
2+
3+
## Supported Versions
4+
5+
react-tabs encourages users to upgrade to the [latest version](https://github.com/reactjs/react-tabs/releases).
6+
7+
Only the latest released version of react-tabs is actively supported. When reporting bugs or security issues, we encourage you to first upgrade to the latest version and confirm that the problem still exists.
8+
9+
We patch bugs and security relevant issues in the latest version and recommend upgrading. react-tabs goes to great length to ensure backwards compatibility so upgrading is almost always painless.
10+
11+
We will backport security fixes if needed to the last 2 previous major versions.
12+
13+
| Version | Supported |
14+
| ------- | ------------------ |
15+
| [v6](https://github.com/reactjs/react-tabs/releases) | :white_check_mark: |
16+
| [v5](https://github.com/reactjs/react-tabs/releases) | :white_check_mark: |
17+
| [v4](https://github.com/reactjs/react-tabs/releases) | :white_check_mark: |
18+
| v3 or older | :x: |
19+
20+
## Reporting a Vulnerability
21+
22+
Security vulnerabilities should be reported by drafting a [Security Advisory](https://github.com/reactjs/react-tabs/security/advisories/new) directly on github or through [Tidelift](https://tidelift.com/docs/security).
23+
24+
You can also reach out to the maintainer directly at Keybase `@danez_gh` or Matrix `@danez_gh:matrix.org`

0 commit comments

Comments
 (0)