# ComposeGuard security.txt — RFC 9116 # # Public-mirror boundary: PUBLIC (exported to the public GitHub mirror). # # This file MUST be served over HTTPS at the well-known path: # https:///.well-known/security.txt # The project website (website/) carries a byte-identical copy at # website/.well-known/security.txt, so the Canonical host # https://composeguard.com/.well-known/security.txt serves it (MAINT-144; # the drift check keeps the two copies identical). A manager per-deployment # HTTP route to also serve it is a secondary open item. # # OPEN ITEM: an OpenPGP key (Encryption:) for encrypted reports is not yet # published; until it is, the contact accepts plain-text reports. See # ../SECURITY.md. # # OPEN ITEM: the Expires date is a PLACEHOLDER (2027-06-10) and MUST be # refreshed at least annually — an expired security.txt is invalid per # RFC 9116. Keep this value less than one year in the future. Contact: mailto:security@composeguard.com Expires: 2027-06-10T00:00:00.000Z Preferred-Languages: en, de Policy: https://composeguard.com/SECURITY.md Canonical: https://composeguard.com/.well-known/security.txt