A security researcher drops a new exploit PoC. A critical security tool releases a major update. A CVE gets a working exploit added to a tracking repo.
How do you find out? If you're lucky, someone tweets about it. If you're not, you discover it three days later during your weekly GitHub scroll.
What if you could track the repos and researchers that matter, and get notified the moment something happens?
The Problem with GitHub Discovery
GitHub is where security research lives. Exploit databases. Security tools. CVE tracking repos. Researcher side projects that become industry standards.
But staying current is hard:
- No central feed - Each repo is its own silo
- Star and forget - How many repos have you starred but never check?
- FOMO scrolling - Endless browsing hoping to catch something good
- Release chaos - Major updates buried in notification noise
You end up either missing important releases or spending hours browsing GitHub.
GitHub Tracker
{P}eelSec's GitHub Tracker solves this. Track repositories, users, and organizations. Get notified when activity happens.
What You Can Track
| Entity Type | What You Get |
|---|---|
| Repositories | Releases, commits, issues with CVE tags |
| Users | New repos, activity on tracked projects |
| Organizations | New repos, releases across all org projects |
What Gets Monitored
For each tracked repo:
- New releases - Version updates, release notes
- Significant commits - Especially to main/master
- CVE-tagged issues - Vulnerability disclosures
- Security advisories - Official security notifications
Setting Up Tracking
Adding a Repository
- Go to GitHub in the sidebar
- Click Add Repository
- Enter the repo URL (e.g.,
https://github.com/projectdiscovery/nuclei) - Click Track
The repo appears in your tracked list. Activity starts flowing.
Adding a User or Organization
Same flow, different URL type:
- User:
https://github.com/swisskyrepo - Organization:
https://github.com/projectdiscovery
Track a prolific researcher. Get their new projects automatically.
The Dashboard
Your GitHub Tracker dashboard shows:
| Repo | Last Activity | Type | Status |
|---|---|---|---|
| nuclei | 2 hours ago | Release v3.1.0 | New |
| PayloadsAllTheThings | 1 day ago | Commit | Seen |
| CVE-2024-XXXX | 3 days ago | Issue | Seen |
Color coding:
- New activity you haven't seen
- Activity you've reviewed
- Inactive repos (no recent changes)
Click any row to see details.
Recommended Repos to Track
Exploit Databases
| Repo | Description |
|---|---|
trickest/cve | CVE PoC tracking |
nomi-sec/PoC-in-GitHub | GitHub CVE PoCs |
offensive-security/exploitdb | Exploit-DB mirror |
Security Tools
| Repo | Description |
|---|---|
projectdiscovery/nuclei | Vulnerability scanner |
OWASP/CheatSheetSeries | Security cheat sheets |
danielmiessler/SecLists | Security testing lists |
Research Collections
| Repo | Description |
|---|---|
swisskyrepo/PayloadsAllTheThings | Payload collection |
HackTricks-wiki/hacktricks | Hacking techniques |
SigmaHQ/sigma | Detection rules |
Vendor Security
| Repo | Description |
|---|---|
MicrosoftDocs/security-updates | Microsoft patches |
cisagov/CHIRP | CISA tools |
Notifications
Configure how you want to be notified:
Notification Types
| Type | Best For |
|---|---|
| In-app only | Nice-to-know repos |
| Email on releases | Critical tools |
| Email on all activity | High-priority tracking |
Digest Options
| Option | Behavior |
|---|---|
| Immediate | Email per event |
| Daily digest | One email, all activity |
| Weekly summary | Weekly rollup |
Start with daily digests. Immediate notifications for repos where timing matters (exploit drops, CVE PoCs).
Real Scenarios
Scenario 1: The Tool Update
You use Nuclei for vulnerability scanning. A new version drops with critical detection templates.
Without tracking: You find out next week when someone mentions it in Slack.
With tracking: Notification arrives within an hour. You're running the new version by lunch.
Scenario 2: The Exploit Drop
A CVE you're monitoring gets a public PoC added to a tracking repo.
Without tracking: You discover it when it shows up in threat intel feeds (if it does).
With tracking: Notified immediately. You can assess impact before it's widely known.
Scenario 3: The New Research
A security researcher you follow creates a new repo for a novel attack technique.
Without tracking: You miss it entirely until it becomes famous.
With tracking: You're an early adopter. You've already tested it by the time others are discovering it.
Integration with Threat Feed
GitHub activity integrates with your main {P}eelSec feed:
- CVE-tagged issues appear as threat items
- Release notes for tracked tools show in your timeline
- Exploit PoCs get auto-correlated with CVE data
One unified view. GitHub activity alongside other intel sources.
CVE Correlation
When you track CVE-related repos (like trickest/cve), {P}eelSec automatically:
- Detects new CVE entries
- Matches them to CVEs in your threat feed
- Adds "Exploit Available" badges to affected items
- Links directly to the PoC
A CVE with a working exploit is more urgent than one without. Now you'll know.
Team Tracking
For teams:
- Shared tracking list - Everyone sees the same repos
- Collaborative curation - Team members can add repos
- Unified notifications - Team-wide or individual preference
Build a shared knowledge base of important repos.
Limits by Tier
| Tier | Tracked Repos | Tracked Users/Orgs |
|---|---|---|
| Free | 3 | 2 |
| Pro | Unlimited | Unlimited |
| Team | Unlimited | Unlimited |
Free tier is enough to try it. Upgrade when you need more.
Try It
- Go to GitHub in the sidebar
- Add a repo you care about
- Enable notifications
- Wait for activity
Next time that repo has a release, you'll know immediately.
Because security research shouldn't require constant GitHub scrolling. Track what matters. Get notified when it moves.
Enjoyed this post?
Subscribe to get new posts and product updates delivered to your inbox.