Open
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## dev #2007 +/- ##
======================================
- Coverage 92% 92% -0%
======================================
Files 416 436 +20
Lines 34690 35642 +952
======================================
+ Hits 31644 32504 +860
- Misses 3046 3138 +92 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
TheTechromancer
force-pushed
the
3.0
branch
2 times, most recently
from
5cb7f10 to
1a36dae
Compare
added 23 commits
March 18, 2025 11:43
openssl_dev_headers is not a real binary, so which() always fails, causing the full ansible playbook + ansible-galaxy collection install to run every time (~15s). Added _core_dep_satisfied() to check for the actual header file instead. Also deferred ansible/tldextract/sudo setup to only run when there's actually something to install. Reduces single module test time from ~17s to ~2s.
liquidsec
approved these changes
Feb 27, 2026
…rmatting
- git clean before branch checkout to prevent uv.lock conflicts when
switching between Poetry/UV branches
- refactor comment posting so both success and failure paths search for
existing comments before creating new ones
- fix fallback message using template literal instead of .join('\\n')
which produced literal \n characters instead of newlines
Fix benchmark report: uv.lock conflict, duplicate comments, broken formatting
Fix install_core_deps running ansible on every test invocation
liquidsec
approved these changes
Feb 28, 2026
Fix omitted event types leaking to console output
…parsing Fix double-parsing of targets in BBOTTarget init
Shodan Enterprise Module
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
BBOT 3.0 "
blazed_elijah" contains changes needed to store BBOT data in a persistent database. The idea is to release it alongside BBOT server, a tiny CLI-only database. This will be paired with a series of blog posts showing how BBOT server can be used on the command line to script out bug bounty hunting, threat intel, and ASM (i.e. running scheduled scans, exporting to CSV, diffing results over time, etc.).Together, BBOT 3.0 and BBOT server will give us a solid foundation to build a bunch of other useful tooling, like asset inventory. Sometime in the future, it may also be useful to frontend.
Breaking changes
1.
.dataand.data_jsonevent fieldsThe main breaking change in BBOT 3.0 is that the name of the
.datafield is different based on whether it's astrordict..data: string.data_json: dictionaryThe
siem_friendlyoption has been removed, since BBOT data is now SIEM-friendly by default.2. Changes to vulnerabilities
The
VULNERABILITYevent type has been removed in favor ofFINDING, which now has several improvements:namefield which holds a generic description common to all findings of the same type. This makes it easier to collapse and categorize them.confidencefieldseverityfieldFeatures
Potential changes