Security

Static journal on Cloudflare Workers with hardened headers (HSTS, CSP, frame deny, nosniff, referrer policy, Permissions-Policy). No logins or public forms.

Engagement metrics are snapshots at capture — not a live feed from X. Numbers refresh when the journal is rebuilt with a new capture.

Threat intel signal feed

Machine-readable signals for product security, cybersecurity, library/supply-chain concerns, and related operator notes. Intended for downstream PSIRT systems to pull, cache, and store history — not as an authoritative vulnerability database.

• GET /feeds/threat-intel.json — full feed
• GET /feeds/manifest.json — cheap poll (feed_hash, counts)
• GET /feeds/threat-intel.json?since=ISO8601 — delta by capture/update time
• /feeds/schema/threat-intel-v1.json — schema

Trust model: every item sets trust.authoritative: false, must_enrich: true, and customer_facing_without_review: false.

Urgency field (severity.hint) is an unverified operator guess from post text — values: critical, high, elevated, watch, needs_score, low. It is not CVSS/EPSS/KEV. Each feed rebuild re-evaluates urgency and sets severity.assessed_at (last checked) and severity.first_assessed_at. If urgency changes, previous_hint is recorded. Manual updates: edit content/data/urgency-overrides.json then rebuild. severity.cvss is always null on this feed.

Polling: ≤ twice daily is enough for this source. Use If-None-Match / feed_hash / per-item content_hash so your store only processes material changes.

Schema version: 1.0.0 · items in window: 49 · feed hash: 9322a096ef4f1145…

Report issues: alexanderromero@gmail.com · security.txt