[Docs] CHANGELOG still cites security@vigilis.nl as a reporting address #645

New issue

Closed

opened 2026-07-22 16:23:40 +00:00 by brenno · 0 comments

brenno commented

2026-07-22 16:23:40 +00:00

Owner

Found in the main loop while checking publication readiness of the repository.

Evidence: CHANGELOG.md:405 — "contactkaartje in de issuetracker verwees naar security@vigilis.nl, terwijl…". The reporting address is security@librekat.nl (SECURITY.md:20).

The line describes a fault that was fixed, so its presence may well be deliberate — the house style is to leave corrections standing. But the effect on a new reader is that grep -rn "security@" . surfaces two addresses with no indication which is current, and the wrong one is at a domain the foundation does not use for this purpose.

Why this matters: low severity, and arguably by design. Filed so the choice is made explicitly rather than by default, since the changelog is about to become public.

Proposal: either add a half-sentence making clear which address is current, or reword the entry to describe the fault without reproducing the dead address. Related: the URLs throughout COMPLIANCE.md, SECURITY.md:543-545 and CHANGELOG.md:4903 point at the pawprint.vigilis.online forge — correct today, but worth a deliberate decision about whether the canonical public address of an LibreKAT project should live on that host.

Found in the main loop while checking publication readiness of the repository. **Evidence:** `CHANGELOG.md:405` — "contactkaartje in de issuetracker verwees naar `security@vigilis.nl`, terwijl…". The reporting address is `security@librekat.nl` (`SECURITY.md:20`). The line describes a fault that was fixed, so its presence may well be deliberate — the house style is to leave corrections standing. But the effect on a new reader is that `grep -rn "security@" .` surfaces two addresses with no indication which is current, and the wrong one is at a domain the foundation does not use for this purpose. **Why this matters:** low severity, and arguably by design. Filed so the choice is made explicitly rather than by default, since the changelog is about to become public. **Proposal:** either add a half-sentence making clear which address is current, or reword the entry to describe the fault without reproducing the dead address. Related: the URLs throughout `COMPLIANCE.md`, `SECURITY.md:543-545` and `CHANGELOG.md:4903` point at the `pawprint.vigilis.online` forge — correct today, but worth a deliberate decision about whether the canonical public address of an LibreKAT project should live on that host.

brenno added the

docs

label

2026-07-22 16:23:40 +00:00

brenno referenced this issue from a commit

2026-07-22 17:07:10 +00:00

docs(changelog): geef 0.1.0 een kop, en haal het dode adres eruit (#609 #645)

brenno referenced this issue from a commit

2026-07-22 17:10:07 +00:00

docs: haal negen achterhaalde beweringen uit de publieke teksten

brenno referenced this issue from a commit

2026-07-22 17:12:00 +00:00