Repository navigation
feat(capabilities): add governed BeeScan HTTP probing - #302
Merged
Merged
Conversation
beesyst
force-pushed
the
feat/301-bs1-beescan-governed-http-probe
branch
from
October 14, 2026 19:37
f5251bd to
973d977
Compare
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
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
Integrate BeeScan as an optional BeeAgent module and implement one real, explicitly authorized, host-governed HTTP probe using ProjectDiscovery httpx.
Existing ROP and BeeDrill dispatch and default configuration remain unchanged.
Related issue
Closes #301
Depends on beesyst/beescan#8 and its reviewed immutable revision.
Iteration
Scope
Included: optional BeeScan installation, module registration, host approval, provider pinning, restricted egress, fixed HTTP probe, CLI, artifacts, integration tests, CI and operational documentation.
Excluded: generic scanner execution, crawling, Nuclei, Findings, AI, BeeUI, database and changes to Solana execution.
Changes
config/settings.yml/core/settings.py— disabled-by-default registration and validated approval.config/start.py— BeeScan bootstrap/probe CLI.core/beescan_policy.py— approval and execution policy.core/beescan_http_runner.py— isolated provider execution and destination enforcement.core/beescan_probe.py— strict output parser, handoff and artifact lifecycle.tests/test_beescan_probe.py— security and contract regressions.integration_tests/test_beescan_lab.pyand fixtures — explicit real-provider laboratory gate..github/workflows/ci.yml— PR/main CI.The final delivery must include a reproducible BeeScan dependency pin and corresponding CI installation.
Config / Contract impact
config/settings.ymlcontract changedNew configuration
modules.registry[].enabledcontrols module loading.beescan.probe_enabledandbeescan.approvalindependently control network execution.New artifacts
bootstrap_health.json,module_result.json,http_probe_status.json,http_observation.jsonand bounded evidence JSON.Verification level
Base checks
Quality / security
Test details
Latest reported results before the final dependency/CI adjustment:
Full and clean-checkout checks must be rerun after the immutable BeeScan dependency pin is added.
Manual scenarios checked
host/host_ipwith no false-success artifacts.Artifacts
Verified complete Observation, status and evidence linkage for real authorized lab runs.
Failed/refused runs retain bounded status artifacts without successful Observations or evidence references.
Security review
The pinned httpx 1.12.0 Go 1.27.2 rebuild has a documented profile-specific advisory applicability review. This does not certify arbitrary provider options or future builds.
Checklist
Limitations / follow-ups
Notes
BeeAgent version remains
0.72.0.BeeScan stays disabled by default, ROP stays disabled, and BeeDrill remains enabled. No automatic network authority is introduced.