From d709233b189569e00ac6acbddb596fce4f82926f Mon Sep 17 00:00:00 2001 From: Jason Norch Date: Thu, 12 Nov 2026 15:24:32 -0500 Subject: [PATCH] Take the source section and the GitHub links off the home page The home page had a section headed "Read the code before you send it anything", built around the source being published, with a link to the repository. Jason does not want the company page advertising that, so the whole section is removed rather than reworded. Two other links pointed at GitHub: one in the footer, and the contact panel's vulnerability-reporting link to SECURITY.md. Both are gone. The contact panel now gives security@securityaccelerated.com for security reports directly. SECURITY.md is untouched and still names the support address. Assisted-by: Claude Fable 5.2 --- internal/handler/changelog.yaml | 8 ++++++ internal/handler/home.html | 44 +-------------------------------- 2 files changed, 9 insertions(+), 43 deletions(-) diff --git a/internal/handler/changelog.yaml b/internal/handler/changelog.yaml index ea20a8a..eb3a9c2 100644 --- a/internal/handler/changelog.yaml +++ b/internal/handler/changelog.yaml @@ -10,6 +10,14 @@ # terms (#91). An entry a later release reversed keeps its text and gains a # "superseded in vX" note, rather than being hidden or rewritten. +- version: v1.1.3 + date: 2026-11-12 + changes: + - text: "The home page is shorter: the section between the plans and the contact details is gone. Security reports now go to security@securityaccelerated.com, shown in the contact details" + audience: public + - text: "Removed the home page's \"Read the code before you send it anything\" section, with its four commitments, and the page's three links to GitHub (the source, the footer link, and SECURITY.md). SECURITY.md itself still names the support address" + audience: internal + - version: v1.1.2 date: 2026-11-12 changes: diff --git a/internal/handler/home.html b/internal/handler/home.html index 023b959..352282c 100644 --- a/internal/handler/home.html +++ b/internal/handler/home.html @@ -339,18 +339,6 @@ .home-plans-foot { max-width: 64ch; margin: 28px 0 0; } - /* ----- Approach ----- */ - .home-commitments { - display: grid; - grid-template-columns: repeat(2, minmax(0, 1fr)); - gap: 0 64px; - margin: 36px 0 0; - } - - .home-commitments div { padding: 18px 0 22px; border-top: 1px solid var(--divider); } - .home-commitments dt { color: var(--ink); font-size: 17px; font-weight: 700; } - .home-commitments dd { max-width: 46ch; margin: 6px 0 0; } - .home-links { display: flex; flex-wrap: wrap; @@ -409,7 +397,6 @@ @media (max-width: 900px) { .home-split, .home-plans, - .home-commitments, .home-contact dl { grid-template-columns: minmax(0, 1fr); } } @@ -576,34 +563,6 @@

Pro

A Pro key is self-service: subscribe, copy the key from the confirmation page, and rotate it yourself whenever you need to. The docs have the full comparison.

-
-

Read the code before you send it anything

-

The source is published so you can evaluate the service before you trust it with a query. It is source-available with all rights reserved, not open source.

-
-
-
You get what worked
-
A lookup that fails says why in a per-result errors array. The rest of the response still arrives.
-
-
-
Failures are never cached
-
Only successful lookups are stored, so an upstream outage is not replayed to you later as an answer.
-
-
-
One path out for lookups
-
Every HTTP and TLS connection a lookup makes goes through a single SSRF-prevention layer that checks the address at dial time, after DNS resolution.
-
-
-
The release process is in the repo
-
How a version reaches production, and the approval it waits for, is written down next to the code.
-
-
- -
-

Contact

@@ -613,7 +572,7 @@

Contact

Security reports
-
How to report a vulnerability
+
security@securityaccelerated.com
@@ -624,7 +583,6 @@

Contact