From 414bcaf34852788417d91bcd9f377f42829ffef0 Mon Sep 17 00:00:00 2001
From: Erb3 <49862976+Erb3@users.noreply.github.com>
Date: Thu, 22 Aug 2024 19:10:51 +0200
Subject: [PATCH] fix(docs): reduce security.txt expiry

This addresses a concern where the security.txt has a long expiration date. Someone could treat this as "use this until then", which we don't want since it's a long time. The specification recommends no longer than one year, as it is to mark as stale.

From the RFC:

> The "Expires" field indicates the date and time after which the data contained in the "security.txt" file is considered stale and should not be used (as per Section 5.3). The value of this field is formatted according to the Internet profiles of [ISO.8601-1] and [ISO.8601-2] as defined in [RFC3339]. It is RECOMMENDED that the value of this field be less than a year into the future to avoid staleness.

Signed-off-by: Erb3 <49862976+Erb3@users.noreply.github.com>
---
 apps/frontend/src/public/.well-known/security.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/apps/frontend/src/public/.well-known/security.txt b/apps/frontend/src/public/.well-known/security.txt
index 12b44e712..c9483bfb6 100644
--- a/apps/frontend/src/public/.well-known/security.txt
+++ b/apps/frontend/src/public/.well-known/security.txt
@@ -1,5 +1,5 @@
 Contact: mailto:jai@modrinth.com
-Expires: 2030-01-01T00:00:00.000Z
+Expires: 2025-06-01T00:00:00.000Z
 Preferred-Languages: en
 Canonical: https://modrinth.com/.well-known/security.txt
 Policy: https://modrinth.com/legal/security