Version v0.1.22This page as markdown
PrompTugal.news· Weather Designs Pay for what you read · free here

Not a warning service. For warnings and what to do now, follow IPMA and ANEPC. In an emergency call 112.

Security

Every vulnerability, bug and breach found on weather.promptugal.news, with its severity, the fix and its commit, and the threat models of what runs on its own.

Published at Dinis Cruz's word (18 November 2026, about 15:15 UTC): "make sure that these vulnerabilities and bugs and report are published on the website". A fixed finding is published in full; an open one shows only its title, severity and state until it is fixed. The log for every PrompTugal.news site is at https://promptugal.news/security/.

To report a problem, open an issue at https://github.com/PrompTugal/PrompTugal__News__Weather/issues (for something that should not be public yet, say so in the title and leave out the detail; we will reach you).

Findings

#FindingSeverityWhereFoundByFixState
W-1Links built from fetched or API data accepted any URL scheme, so a javascript: value in the data would have become a clickable link. Text was already HTML-escaped and no page uses innerHTML, so it needed a bad value in data.promptugal.news's output.Mediumscripts/site/generate.mjs, scripts/site/design/*.mjs, scripts/site/timeline.mjs, markdown links in scripts/site/lib.mjs18 Nov 2026, about 15:15 UTCweather.b@'s AppSec review, after events.b@'s XSS finding on events.promptugal.news (passed on by conductor.b@)Every link from data goes through safeHref() (http(s), site-relative or #, else #); the build gate refuses javascript:, data:, vbscript: and file: URLs. Commit 47ef847Fixed
W-2/account/ drew links from paths kept in the browser's own storage without checking them. Only this site's own pages can write that storage, so the risk was small.Lowsrc/assets/reading.js18 Nov 2026, about 15:15 UTCthe same reviewOnly site-relative paths are kept. Commit 47ef847Fixed
W-3The data pull accepted any file that parsed as JSON, with no size cap, timeout or shape check.Lowscripts/sync-data.mjs18 Nov 2026, about 16:20 UTCthe security pre-review pass (Sonnet)A 20 s timeout, a 5 MB cap per file, no redirect to another host, and a shape check per kind; a file that fails keeps the committed copy. This wake's commitFixed
W-4Third-party build actions named by version tag, not by commitLow.github/workflows/pages.yml18 Nov 2026, about 16:20 UTCthe security pre-review passOpen
W-5Page-view events' destination and key read from another site's file without pinning (inactive: no lane open)Lowsrc/assets/obs/obs.js18 Nov 2026, about 16:20 UTCthe security pre-review passOpen
W-6Map files read from a moving branch, not a pinned commitLowscripts/sync-data.mjs18 Nov 2026, about 16:20 UTCthe security pre-review passOpen
W-7The release tag step holds write access to the repositoryInformational.github/workflows/pages.yml18 Nov 2026, about 16:20 UTCthe security pre-review passAccepted for now: it pushes the version tag only
W-8Bug: the hourly rebuild did not run. The schedule added at 15:20 UTC on 18 November never fired (no scheduled run recorded by 17:51 UTC), so pages showed data up to about two hours old.Low.github/workflows/pages.yml18 Nov 2026, 17:51 UTCconductor.b@PrompTugal.dinis, after an agent building on the data reported it was not refreshingPages now read data.promptugal.news in the browser and update when it has newer data (src/assets/live.js); the schedule runs twice an hour. This commitMitigated; open until a scheduled run is seen

No breach is known. No secret, key or private person's data has been found in this repository: the leak scan (scripts/leak-scan.mjs) checks the tracked files and the built site before every release.

Threat models

What runs on its own, what it reads, writes and trusts, what could go wrong and how it is limited. Published 18 November 2026; review by security@PrompTugal.dinis requested. All three are on How it works:

4 front pages, the same data: which should lead?

Dinis chooses; the others stay at /design/.