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>
Modrinth Monorepo
Welcome to the Modrinth Monorepo, the primary codebase for the Modrinth web interface and app. It contains lines of code and has
contributors!
If you're not a developer and you've stumbled upon this repository, you can access the web interface on the Modrinth website and download the latest release of the app here.
Development
This repository contains two primary packages. For detailed development information, please refer to their respective READMEs:
Contributing
We welcome contributions! Before submitting any contributions, please read our contributing guidelines.
If you plan to fork this repository for your own purposes, please review our copying guidelines.
Security
If you discover a security vulnerability within our codebase, please follow our responsible disclosure guidelines.
Support
If you need help with the Modrinth web interface or app, please visit our support page. For general inquiries, you can also join our Discord server.
License
All packages in this repository are licensed under their respective licenses. Refer to the LICENSE file in each package for more information.
