Skip to content

Release PhantomRecon 2.2.0: plugins, reporting, provider controls and automation - #4

Merged
c0d3s3cl4b merged 22 commits into
mainfrom
feature/phantomrecon-2.2
Aug 12, 2026
Merged

c0d3s3cl4b merged 22 commits into
mainfrom
feature/phantomrecon-2.2

Conversation

@c0d3s3cl4b

@c0d3s3cl4b c0d3s3cl4b commented Aug 12, 2026 •

Copy link
Copy Markdown
Owner

PhantomRecon 2.2.0

This PR promotes the 2.2 development line to stable 2.2.0.

Added

  • Python entry-point based third-party plugin discovery via phantomrecon.plugins
  • phantomrecon plugins diagnostics with safe metadata-only discovery by default
  • phantomrecon config effective runtime configuration output
  • unified JSON/HTML reporting with phantomrecon report
  • report directory configuration through PHANTOMRECON_REPORT_DIR
  • HTML escaping for report values
  • per-host shared HTTP throttling via PHANTOMRECON_HTTP_MIN_INTERVAL
  • provider readiness, descriptions, homepage metadata, and JSON diagnostics
  • plugin, reporting, config, and provider unit tests
  • CI smoke tests for plugins, config, providers, and doctor
  • tag-driven GitHub Release automation with wheel/sdist assets

Provider/network behavior

  • shared HTTP retries honor Retry-After
  • per-host request pacing reduces accidental bursts against public data providers
  • provider diagnostics report readiness without sending probe traffic

Version

  • stable version: 2.2.0

Safety

The bounded active DNS and TCP scan behavior from 2.1 remains unchanged. Plugin code is not imported during normal discovery unless --load is explicitly requested.

Ready to merge once the final Python 3.10/3.11/3.12 CI run is green.

@c0d3s3cl4b c0d3s3cl4b changed the title PhantomRecon 2.2: plugins, reporting and release automation Release PhantomRecon 2.2.0: plugins, reporting, provider controls and automation Aug 12, 2026
@c0d3s3cl4b
c0d3s3cl4b marked this pull request as ready for review August 12, 2026 15:44
@c0d3s3cl4b
c0d3s3cl4b merged commit d9cbdb8 into main Aug 12, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant