Skip to content

About

Toolkit & methodology for my daily open-source bug hunt - one verified issue a day

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

7 Commits

Folders and files

Repository files navigation

bug-hunting-kit 🐛

CI

The toolkit behind my daily habit: read one open-source project, file one verified issue.

What's inside

File Purpose
file_issue.py File a GitHub issue from the CLI (stdlib only). Reads GITHUB_TOKEN or the stored git credential.
scan_patterns.py Static scan for four mechanical bug patterns (finally-return, discarded str result, lstrip charset, mutable default). Candidates, not verdicts.
METHODOLOGY.md The bug patterns I hunt for, ranked by hit rate, each born from a real find.

Usage

python file_issue.py --repo owner/repo --title "fix: ..." --body-file issue.md
python scan_patterns.py path/to/repo

Ground rules

  1. Never file what you cannot reproduce or prove from the code path.
  2. Quote the exact source lines (file + line number) in the issue.
  3. Always propose the one-line fix.
  4. Check open issues first; link related ones.
  5. Match the maintainer's language.

Track record

27 issues and 2 PRs across 27 repos, every one with a minimal repro or a line-level code-path proof. One PR merged upstream.

About

Toolkit & methodology for my daily open-source bug hunt - one verified issue a day

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages