Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create security policy #439

Merged
merged 2 commits into from
Jun 27, 2024
Merged

Create security policy #439

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
22a7656
Create SECURITY.md
dcastil Jun 27, 2024
066db3b
Add backup email to security policy
dcastil Jun 27, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions .github/SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
# Security Policy

## Supported Versions

Security updates are available for the two latest major versions.

In the event of a security vulnerability in tailwind-merge, a patch release with a fix will be made to all affected latest major versions. I.e. if the two latest major versions of tailwind-merge would be `v9.3.4` and `v8.10.0` and a security vulnerability would get discovered which affected all versions from `v6.0.0` to `v9.3.4`, then at least the releases `v9.3.5` and `v8.10.1` would be made to fix the security vulnerability.

## Reporting a Vulnerability

Please report vulnerabilities privately via GitHub at https://github.com/dcastil/tailwind-merge/security.

In case it is not possible to report a vulnerability via GitHub, you can send me an email to metro_comical_03@icloud.com. However, I might change or disable this email address at any time depending on how much spam I get through it.

You can expect an answer from me within 24 hours most of the time. However, if I'm travelling and don't have good reception, it could take up to a few days. Usually I set my GitHub status to busy when I expect to be unresponsive for more than a day.
Loading