BugSeer is designed from the ground up to be an offline-first, zero-telemetry tool.
- No Cloud Dependencies: Source code analyzed by BugSeer never leaves your machine.
- No Network Requests: Core BugSeer operates completely offline without making outbound network requests or telemetry tracking.
- No API Keys Required: Risk scoring, AST static analysis, Git history analysis, and local machine learning run entirely locally on your hardware.
We provide security updates for the active release series of BugSeer:
| Version | Supported |
|---|---|
| 0.1.x | ✅ |
| < 0.1 | ❌ |
If you discover a security vulnerability or privacy bug in BugSeer, please report it responsibly:
- Do not create a public GitHub issue for undisclosed security vulnerabilities.
- Submit your report via GitHub Private Vulnerability Reporting on the repository.
- Alternatively, contact the maintainer directly via GitHub (@rishibanota).
- A description of the vulnerability and potential impact.
- Steps to reproduce or proof-of-concept code.
- Any suggested remediations or mitigations.
- Initial Response: Within 48 hours acknowledging receipt of your report.
- Status Updates: Periodic updates as we assess and patch the issue.
- Public Disclosure: After a patch is released and confirmed by the reporter.