gitwtfhub

wtf is hwpoc?

adysec/hwpoc — explained in plain English

Analysis updated 2026-05-18

46HTMLAudience · developerComplexity · 2/5Setup · easy

TL;DR

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.

Mindmap

mindmap
  root((hwpoc))
    What it does
      Vulnerability data catalog
      Zero day one day n day
      Static site output
    Tech stack
      TOML data files
      Python build scripts
      GitHub Actions
    Use cases
      Track known vulns
      Submit new reports
      Research HW exercises
    Audience
      Security researchers
      Defenders
      Chinese HW participants

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Look up known vulnerabilities by vendor, year, or type before a security exercise.

REASON 2

Submit a newly discovered vulnerability through a GitHub Issue form or pull request.

REASON 3

Track how a vulnerability report moves from submission to reviewed, published data.

What's in the stack?

HTMLPythonTOMLGitHub Actions

How it stacks up

adysec/hwpocbookunt3d/hermes-agent-fadevopssessionsjvr/agentic-ai-demo
Stars464547
LanguageHTMLHTMLHTML
Setup difficultyeasyeasyhard
Complexity2/51/54/5
Audiencedeveloperdeveloperops devops

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · easy Time to first run · 5min
No license information is stated in the README.

Wtf does this do

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.

Yoink these prompts

Prompt 1
Explain the TOML fields used in this vulnerability entry format and how to fill one out correctly.
Prompt 2
Write a GitHub Actions workflow step that parses a TOML file like the ones in docs/2026/ and validates required fields.
Prompt 3
Show me how build-static.py likely converts a folder of TOML files into HTML pages, and suggest improvements.
Prompt 4
Draft a new TOML vulnerability entry for a hypothetical RCE flaw using this project's schema.

Frequently asked questions

wtf is hwpoc?

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.

What language is hwpoc written in?

Mainly HTML. The stack also includes HTML, Python, TOML.

What license does hwpoc use?

No license information is stated in the README.

How hard is hwpoc to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is hwpoc for?

Mainly developer.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.