Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
vulnerability-spoiler-alert — A monitoring hub that watches popular open-source repositories and uses AI to detect when commits are patching security vulnerabilities - often before a CVE is even assigned. Findings are published to a retro-themed website with an RSS feed. | Kitploit
Tools/GitHubGitHub/spaceraccoon/vulnerability-spoiler-alert
Vulnerability AnalysisInformation GatheringThreat IntelligenceLearning & EducationCurated ResourcesAI Security
GitHubspaceraccoon/vulnerability-spoiler-alert

vulnerability-spoiler-alert

A monitoring hub that watches popular open-source repositories and uses AI to detect when commits are patching security vulnerabilities - often before a CVE is even assigned. Findings are published to a retro-themed website with an RSS feed.

View RepositoryWebsite
14926448 days agoReviewed by Kitploit

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

Vulnerability Spoiler Alert

Know about security patches before the CVE drops.

GitHub Actions Claude AI OpenAI License: MIT

View Live Site | Subscribe via RSS


A monitoring hub that watches popular open-source repositories and uses AI to detect when commits are patching security vulnerabilities - often before a CVE is even assigned. Findings are published to a retro-themed website with an RSS feed.

Origin & Inspiration

This project is an example usage of spaceraccoon/vulnerability-spoiler-alert-action by Eugene Lim ().

@spaceraccoon

The original concept and research is documented in the blog post Discovering Negative Days: LLM Workflows for Vulnerability Research, which explores using LLMs to identify security patches before CVEs are assigned - turning the typical "zero-day" into a "negative-day" by catching vulnerabilities in the window between the fix landing and public disclosure.

How It Works

root@kitploit:~
                Every 6 hours
                      |
                      v
  +-------------------------------------------+
  |           GitHub Actions Cron             |
  +-------------------------------------------+
                      |
                      v
  +-------------------------------------------+
  |  vulnerability-spoiler-alert-action       |
  |  scans repos listed in the workflow       |
  +-------------------------------------------+
                      |
                      v
  +-------------------------------------------+
  |  Claude AI / OpenAI analyzes each diff   |
  |  - Is this a security patch?              |
  |  - What vulnerability does it fix?        |
  |  - Can we write a PoC exploit?            |
  +-------------------------------------------+
                      |
                      v
  +-------------------------------------------+
  |  Create GitHub Issue with full analysis   |
  +-------------------------------------------+
                      |
                      v
  +-------------------------------------------+
  |  Rebuild website + RSS                    |
  |  Deploy to GitHub Pages                   |
  +-------------------------------------------+

Monitored Repositories

ProjectRepository
Expressexpressjs/express
Node.jsnodejs/node
Djangodjango/django
Flaskpallets/flask
Railsrails/rails
Apache HTTPDapache/httpd
nginxnginx/nginx
Grafanagrafana/grafana

Verifying Findings

Add labels to issues to classify findings:

LabelMeaning
true-positiveA real vulnerability, manually or automatically verified. Shown as a green VERIFIED badge until a CVE is assigned, then CONFIRMED
cve:CVE-<ID>A matching CVE (applied automatically by the CVE checker, or manually). Promotes a verified finding to CONFIRMED. Only a real CVE counts — a GHSA-only advisory does not promote
false-positiveNot a real vulnerability - dimmed and moved to a collapsible section

A finding with true-positive but no cve:CVE-… label is verified — confirmed real but still in the "negative-day" window before a CVE drops. The CVE checker keeps re-checking verified findings until a CVE is matched.

The site automatically rebuilds when labels are added or removed.

Setup

1. Fork this repository

Click the Fork button at the top right.

2. Add secrets

Go to Settings > Secrets and variables > Actions and add either:

SecretDescription
ANTHROPIC_API_KEYYour Claude API key from console.anthropic.com
OPENAI_API_KEYYour OpenAI API key from platform.openai.com

The GITHUB_TOKEN is provided automatically by GitHub Actions. You only need to add the key for the AI provider you intend to use.

Update monitor.yml to specify your preferred provider and model.

3. Enable GitHub Pages

Go to Settings > Pages and set source to GitHub Actions.

4. Enable workflows

Go to the Actions tab and enable workflows. The monitor runs every 6 hours automatically.

You can trigger it manually via Actions > Monitor Vulnerabilities > Run workflow.

Configuration

Monitored Repositories

Edit the repositories JSON array in .github/workflows/monitor.yml to add or remove repositories.

Cron Schedule

By default, the monitor runs every 6 hours. Edit the cron expression in .github/workflows/monitor.yml:

root@kitploit:~
schedule:
  - cron: '0 */6 * * *'  # Every 6 hours

Architecture

  • Zero dependencies - the site build script uses only Node.js built-in APIs
  • Static site - plain HTML + RSS, deployed via GitHub Pages
  • GeoCities theme - because security advisories deserve the Web 1.0 treatment

License

MIT License - see LICENSE for details.

Disclaimer

This tool is for defensive security research and authorized security testing only. Always follow responsible disclosure practices.

Download Tool