Engineering
How BugPartner is built
BugPartner is an engineering project first. These are the decisions that shape it — each one reflected in the real feature set.
One provider abstraction
Shodan, Censys, VirusTotal, urlscan, and SecurityTrails all sit behind a single Provider Manager, so adding or swapping a source doesn't ripple through the codebase.
Filter before you look
The false-positive removal engine runs before anything reaches a human, so review time is spent on findings that matter.
Validate before you report
A separate validation engine confirms findings are real and reachable — reports only contain what held up.
Bring your own model
Multiple AI providers are supported, with optional local LLMs when analysis needs to stay private.
Alert in real time
Validated, high-signal findings are pushed over Telegram as they land.
Built to extend
A plugin-ready architecture keeps new providers and modules additive, not invasive.
Data flow
Discovery feeds filtering, filtering feeds validation, and only validated findings are analyzed and reported.
target
│
▼
┌─────────────────────────────┐
│ Provider Manager │ shodan · censys · virustotal
│ passive + active discovery │ urlscan · securitytrails
└──────────────┬──────────────┘
▼
┌──────────────────────────┐
│ False-Positive Removal │
└────────────┬─────────────┘
▼
┌──────────────────────────┐
│ Validation Engine │ confirm real + reachable
└────────────┬─────────────┘
▼
┌──────────────────────────┐
│ AI Analysis (multi / │ optional local LLM
│ local model support) │
└────────────┬─────────────┘
┌───────┴────────┐
▼ ▼
┌───────────┐ ┌──────────────┐
│ Reports │ │ Telegram │
└───────────┘ └──────────────┘