zan8in/afrog

A Security Tool for Bug Bounty, Pentest and Red Teaming.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 hour ago
Added to GitGenius on September 15th, 2026
Created on February 24th, 2022
Open Issues & Pull Requests: 111 (+0)
GitHub issues: Enabled
Number of forks: 484
Total Stargazers: 4,419 (+0)
Total Subscribers: 44 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 27.8 hours
Mean response time: 9.8 days
90th percentile: 21.2 days
Tracked items: 62

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 60
New in 7 days: 2
Closed in 7 days: 0
Avg open age: 402 days
Stale 30+ days: 53
Stale 90+ days: 50

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Done (23)
  • ToDo (10)
  • bug (4)
  • Recommendation (1)
  • broadcast (1)
  • good first issue (1)

Most active issues this week

Detailed Description

Afrog is a vulnerability scanner designed for bug bounty, penetration testing, and red teaming operations.

The tool addresses the need for efficient vulnerability detection across target systems by executing proof-of-concept exploits against identified weaknesses. It operates through a collection of PoC rules that can be applied to scan for known vulnerabilities, allowing security professionals to quickly identify exploitable conditions in their target environments.

Teams conducting bug bounty programs, penetration tests, or red team exercises should consider this tool when they need a rule-based scanner that can be customized through PoC definitions. The project is particularly suited for practitioners who want to leverage community-contributed vulnerability checks rather than building detection logic from scratch. The README emphasizes PoC rule quality over quantity, suggesting the tool prioritizes accuracy in its vulnerability definitions.

The project maintains an active issue tracker and accepts contributions from multiple developers. Documentation includes a dedicated guide for writing PoC rules, indicating ongoing investment in making the tool accessible to contributors who want to expand its detection capabilities. The codebase is written in a compiled language, suggesting performance considerations for scanning operations.