From a01b1d8a063a7036fb94ca6badb55482fcfbb3f8 Mon Sep 17 00:00:00 2001 From: Eric Cornelissen Date: Tue, 2 Jul 2024 23:08:28 +0200 Subject: [PATCH] Set expiry date for the Security Policy (#91) Include an expiry date in the security policy primarily as a mechanism to ensure the support timeline can reasonable be updated if no end-of-life date has yet been set. Additionally, it nudges anyone looking at the policy to search for an up-to-date version - which is more helpful for anyone. --- SECURITY.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/SECURITY.md b/SECURITY.md index 2047610..b19d7b1 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -7,6 +7,10 @@ appreciate your efforts to responsibly disclose your findings. Due to the non-funded and open-source nature of the project, we take a best-efforts approach when it comes to engaging with security reports. +This document should be considered expired after 2024-12-31. If you are reading +this after that date, try to find an up-to-date version in the official source +repository. + ## Supported Versions Only the latest release of the project is supported with security updates.