Commit Graph
24 Commits
Author SHA1 Message Date
CVE-BOT 5494c367e8 Trending CVEs update 2026-09-04 19:09 🤖 2026-09-04 19:09:37 +00:00
CVE-BOT 4c3ac69169 Trending CVEs update 2026-09-04 17:09 🤖 2026-09-04 17:09:28 +00:00
CVE-BOT 90a6742893 Trending CVEs update 2026-09-04 14:10 🤖 2026-09-04 14:10:04 +00:00
CVE-BOT bba0a1ac34 Trending CVEs update 2026-09-04 09:09 🤖 2026-09-04 09:09:35 +00:00
CVE-BOT 0f31ce9052 Drop PoC links to deleted repositories 2026-09-04 2026-09-04 08:29:00 +00:00
CVE-BOT b05a5acb33 Sync CVE metadata 2026-09-04 2026-09-04 07:56:23 +00:00
CVE-BOT ee2b6eb533 Update CVE PoCs 2026-09-04 2026-09-04 07:21:28 +00:00
CVE-BOT 6991dd330b Trending CVEs update 2026-09-04 07:09 🤖 2026-09-04 07:09:12 +00:00
CVE-BOT d3f7816a8b Trending CVEs update 2026-09-04 03:09 🤖 2026-09-04 03:09:05 +00:00
CVE-BOT 7bfde05f77 Trending CVEs update 2026-09-04 01:49 🤖 2026-09-04 01:49:53 +00:00
CVE-BOT fc1595d0af Trending CVEs update 2026-09-03 18:34 🤖 2026-09-03 18:34:03 +00:00
CVE-BOT 14388d3ffa Sync exploit archives 2026-09-03 🤖 2026-09-03 09:16:13 +00:00
CVE-BOT 968d7e94f0 Sync CVE metadata 2026-09-03 2026-09-03 08:00:09 +00:00
CVE-BOT 7ace47c9fc Update CVE PoCs 2026-09-03 2026-09-03 07:19:02 +00:00
CVE-BOT 0f46f3180a Sync nuclei templates 2026-09-02 🤖 2026-09-02 08:52:55 +00:00
CVE-BOT a124d64067 Update CVE PoCs 2026-09-02 2026-09-02 07:14:07 +00:00
CVE-BOT 3c420d723b Trending CVEs update 2026-09-02 01:41 🤖 2026-09-02 01:41:49 +00:00
0xMarcio aad1789a71 Keep published counts synchronized 2026-09-02 00:54:09 +02:00
CVE-BOT ec0fae9788 Trending CVEs update 2026-09-01 17:43 🤖 2026-09-01 17:43:44 +00:00
0xMarcio 81017c9871 Expand CVE PoC coverage and metadata 2026-09-01 19:01:07 +02:00
0xMarcio f140e13160 Repair the README pipeline after the move
Moving the data files into index/ left three references behind in .github,
and the hourly job has been failing to stage its own output since. The
README has been advertising 104,016 CVEs with PoCs while the site served
89,125, and every KEV marker had dropped out of its table because the
catalogue was being read from a path that no longer exists.

Figures come from the same count build_site publishes, so the badges, the
hero card and the site cannot disagree again.
2026-09-01 15:50:08 +02:00
CVE-BOT d874588866 Trending CVEs update 2026-09-01 08:34 🤖 2026-09-01 08:34:22 +00:00
CVE-BOT 188f0646c5 Trending CVEs update 2026-09-01 03:42 🤖 2026-09-01 03:42:54 +00:00
0xMarcio 2ed7386028 Give the README a banner and cut it back to the useful parts
The README opened on a bare heading and five year tables, said nothing about
what the project is, and never linked the site. Anyone landing on the repo had
to guess. It now leads with a generated banner carrying the live index totals,
a badge row, and tables trimmed to what fits a table cell.

hero.py draws the banner and the social card as self-contained SVG, since
GitHub proxies README images and drops anything the file has to fetch for
itself. It counts the corpus through build_site's own parser rather than a
second guess at what counts as a PoC, so the banner cannot drift from the site
header, and leaves the figures in docs/stats.json for the README build to
quote. If the count fails it falls back to the deployed site and, failing
that, writes nothing at all: a banner reading zero is worse than yesterday's.

Badges describing the index are baked in at build time so they always match
the banner and cannot degrade to "resource not found"; the two that describe
live GitHub state carry a stamp that defeats the image proxy cache.

The sweep now runs hourly instead of every six hours. It takes under two
minutes and the repository shows up in "recently updated" far more often.

Also adds the OpenGraph tags the site never had, so a shared link renders a
card instead of a bare URL.
2026-09-01 04:28:33 +02:00