Skip to content

docs: use mailto scheme for security email in SECURITY.md - #2588

Merged
odinserj merged 1 commit into
HangfireIO:mainfrom
FirmaSpring:fix/security-email-mailto
Aug 28, 2026
Merged

docs: use mailto scheme for security email in SECURITY.md#2588
odinserj merged 1 commit into
HangfireIO:mainfrom
FirmaSpring:fix/security-email-mailto

Conversation

@FirmaSpring

Copy link
Copy Markdown
Contributor

Problem

SECURITY.md still writes the security contact as:

Please email us at [security@hangfire.io](security@hangfire.io) with details

Without a mailto: scheme this renders as a relative URL. Verified with a GET:

curl -sL -o /dev/null -w "%{http_code} %{url_effective}\n" \
  "https://github.com/HangfireIO/Hangfire/blob/main/security@hangfire.io"
# 404

So the rendered link leads to a 404 page instead of opening a mail client.

README.md already received the mailto: prefix in 8c2e32e; SECURITY.md was left out.

Solution

Use mailto:security@hangfire.io as the link target in SECURITY.md, matching the already-fixed README.

Verification

Markdown-only change. Checked open and closed PRs for prior mailto/security-link fixes on SECURITY.md and found none.

SECURITY.md still links the security contact as (security@hangfire.io), which renders as a relative URL that GET 404s under the repo. README.md got the mailto: prefix in 8c2e32e; apply the same fix here.

Co-authored-by: FirmamentalSpring <287222957+FirmaSpring@users.noreply.github.com>
@odinserj

Copy link
Copy Markdown
Member

Thank you @FirmaSpring!

@odinserj
odinserj merged commit 02e82f8 into HangfireIO:main Aug 28, 2026
2 checks passed
This was referenced Aug 28, 2026
This was referenced Aug 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

2 participants