git404hub

what is ave fr?

adysec/ave — explained in plain English

Analysis updated 2026-05-18

26JavaScriptAudience · ops devopsComplexity · 2/5Setup · easy

tl;dr

A public vulnerability knowledge base that aggregates CVE and exploit data into structured records and a searchable browsing website.

vibe map

mindmap
  root((AVE))
    What it is
      Vulnerability knowledge base
      Unified AVE IDs
      Structured TOML data
    Website features
      Search and filter
      Severity sorting
      Detail pages
    Data sources
      NVD
      CVE
      GitHub Advisory
    Architecture
      GitHub Code Search API
      GitHub Pages hosting
      GitHub Actions deploy

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

what do people make with this?

VIBE 1

Browse a searchable list of tracked vulnerabilities filtered by severity level.

VIBE 2

Check whether a public proof of concept or exploit exists for a specific CVE.

VIBE 3

Look up remediation advice and reference links for a specific vulnerability.

VIBE 4

Share a bookmarked search or filter view of the vulnerability list via URL.

what's the stack?

JavaScriptTOMLGitHub PagesGitHub Actions

how it stacks up fr

adysec/aveitsmeinayath/visualdbjohunsang/tauri-dev-screen-cli
Stars262626
LanguageJavaScriptJavaScriptJavaScript
Setup difficultyeasyeasymoderate
Complexity2/52/52/5
Audienceops devopsresearcherdeveloper

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

how do i run it?

Difficulty · easy time til it works · 5min

The published site is static and browsable with no setup, the underlying data collection code is not open source.

in plain english

AVE is a public security vulnerability knowledge base built for security operations teams. It pulls in vulnerability information from multiple public sources, such as NVD, CVE, and GitHub Advisory, gives each one its own unified AVE tracking number, and stores the details as structured TOML files organized by year. The project also collects and checks known proof of concept and exploit references tied to each vulnerability, so a security team can quickly see whether public exploit code exists for a given issue and how severe it is. The README is clear that the actual code and logic used to crawl and process vulnerabilities from their original sources has not been made public. What this repository shares instead is the resulting data, plus a static website built on top of it and hosted through GitHub Pages. The website lets a visitor browse the vulnerability list with paging, search by keyword or vulnerability ID, and filter by severity level from critical down to unknown. Columns can be sorted by ID, title, severity, date, or score. A sidebar shows how many vulnerabilities, proof of concepts, and exploits exist per year, along with a bar showing the overall severity breakdown. Search terms, filters, and the current page are saved into the page's URL so a specific view can be shared or bookmarked. A detail page for each vulnerability shows its full description, severity score, related CVE aliases, remediation advice, and any linked proof of concept or exploit files found in the repository. Under the hood, the site searches the repository's TOML files directly through GitHub's Code Search and Tree APIs rather than using a separate database, and it automatically rebuilds and redeploys through GitHub Actions whenever new data is pushed to the main branch. The README does not state a license for this project.

prompts (copy fr)

prompt 1
Explain the TOML structure used to store a single vulnerability record in this project.
prompt 2
Show me how the site searches TOML files using the GitHub Code Search API.
prompt 3
How does the severity filtering and sorting work on the vulnerability list page?
prompt 4
Walk me through how GitHub Actions redeploys the site after new data is pushed.

Frequently asked questions

what is ave fr?

A public vulnerability knowledge base that aggregates CVE and exploit data into structured records and a searchable browsing website.

What language is ave written in?

Mainly JavaScript. The stack also includes JavaScript, TOML, GitHub Pages.

How hard is ave to set up?

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

Who is ave for?

Mainly ops devops.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.