From eb07b1dba7d08f6763336a95731462871378fc73 Mon Sep 17 00:00:00 2001 From: Antony Pegg Date: Fri, 21 Aug 2026 12:34:59 -0400 Subject: [PATCH] docs: make the SECURITY.md links clickable The statement URL and the reporting address were bare text. Dave asked for the URL to be a real link on pgedge-safesession#73: GitHub autolinks it, but nothing guarantees another viewer will, and the two actionable things in a security policy should not depend on a renderer. The published statement at docs.pgedge.com/security already writes the address as an explicit mailto link, so this keeps the two documents consistent. coldfront#80 merged before that review landed, so this is the follow-up. Identical across every repo carrying this file. --- SECURITY.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/SECURITY.md b/SECURITY.md index 3ba2905..33ebccb 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -2,8 +2,9 @@ ## Reporting a Vulnerability -Please report security vulnerabilities to **security@pgedge.com**, which -reaches the pgEdge security team. +Please report security vulnerabilities to +[**security@pgedge.com**](mailto:security@pgedge.com), which reaches the +pgEdge security team. Please do not open a public issue for a suspected vulnerability. @@ -25,7 +26,7 @@ What is in scope, our safe harbour terms, and how we handle coordinated disclosure and CVE identifiers are all set out in the pgEdge Vulnerability Disclosure Statement: -**https://docs.pgedge.com/security** +[**https://docs.pgedge.com/security**](https://docs.pgedge.com/security) You may test this software freely in an environment you control. Testing pgEdge Cloud requires prior written authorisation — see the statement.