Look up known vulnerabilities by vendor, year, or type before a security exercise.
Submit a newly discovered vulnerability through a GitHub Issue form or pull request.
Track how a vulnerability report moves from submission to reviewed, published data.
| adysec/hwpoc | bookunt3d/hermes-agent-fa | devopssessionsjvr/agentic-ai-demo | |
|---|---|---|---|
| Stars | 46 | 45 | 47 |
| Language | HTML | HTML | HTML |
| Setup difficulty | easy | easy | hard |
| Complexity | 2/5 | 1/5 | 4/5 |
| Audience | developer | developer | ops devops |
Figures from each repo's GitHub metadata at analysis time.
This repository is a vulnerability information library built around HW, a term for organized network defense exercises that happen periodically in China. It collects data about zero day, one day, and n day vulnerabilities, meaning flaws that are brand new, recently disclosed, or already well known and patched. The project moved here after outgrowing a shared Tencent Docs spreadsheet that had a limit on how many people could access it. Each vulnerability is stored as its own small TOML file, a simple text format for structured data, and the files are organized into folders by year. As of this writing the collection holds roughly 325 entries from 2023, 455 from 2024, 333 from 2025, and a growing count for 2026. People can add new vulnerability reports in three ways. The recommended path is submitting a GitHub Issue through a form on the project's website, which gets turned into a proper entry once a maintainer reviews and approves it, at which point an automated GitHub Actions workflow extracts the details and rebuilds the site. The second option is opening a pull request that adds a new TOML file directly to the correct year's folder, following a template that records the vendor, vulnerability name, type such as remote code execution, affected versions, exploit path, technical detail or proof of concept, a suggested fix, the date, and a label marking it zero day, one day, or n day. The third option is simply emailing the vulnerability details to the maintainer. Behind the scenes, Python scripts convert the TOML source files into a static HTML website, and a separate script processes incoming GitHub Issues automatically once they are approved. The repository also includes a dark mode stylesheet, a custom domain configuration, and settings that turn off Jekyll processing for GitHub Pages. The project is listed as HTML because that is the generated site output, not application code. It works as a community maintained reference catalog for security researchers and defenders tracking known and emerging vulnerabilities, particularly around China's periodic HW security exercises.
A community maintained catalog of security vulnerabilities (0day/1day/nday) tied to China's periodic HW network defense exercises, stored as TOML files and rendered as a static site.
Mainly HTML. The stack also includes HTML, Python, TOML.
No license information is stated in the README.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.