Skip to content

PerfektBlue v2.1.0 — Bluetooth-first adaptive framework

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 22 Jun 20:59
v2.1.0
bec4725

PerfektBlue 2.1

A focused Bluetooth intelligence console for the complete assessment workflow.

Run perfektblue with no arguments and the framework now opens a polished, stateful terminal
workspace. The interface keeps the active backend, safety policy, selected target, and stored
session count visible while you move through an assessment.

Tip

Existing subcommands and JSON output remain unchanged. The new menu improves interactive use
without breaking scripts or automation.

🧭 New main workspace

Workspace Purpose
Target discovery Scan, compare signal and service context, then select a device
Target workspace Inspect evidence, fingerprint profiles, and preview module plans
Guided assessment Review compatibility and execute policy-safe modules
Environment doctor Validate BlueZ, adapters, dependencies, and local readiness
Sessions & reports Open stored evidence and export standalone HTML or JSON
Intelligence library Review installed target profiles and assessment modules
Settings & safety See runtime thresholds, backend, adapter, and risk policy
Optional CAN plugin Confirm isolated CAN analysis availability

✨ Interaction details

  • Persistent selected-target context across screens.
  • Number and letter shortcuts for fast navigation.
  • Consistent breadcrumbs and back actions.
  • Colored policy, verdict, readiness, and decision states.
  • Progress indicators for discovery, diagnostics, and assessment.
  • Clear empty, invalid-selection, and unsupported-target states.
  • Verdict reference and CLI-equivalent commands in contextual help.
  • Desktop launcher now opens the main workspace directly.

📦 Install

sudo apt install ./perfektblue_2.1.0-1_all.deb
perfektblue

Python wheel:

python3 -m venv .venv
. .venv/bin/activate
python -m pip install ./perfektblue-2.1.0-py3-none-any.whl
perfektblue

✅ Validation

  • 32 automated tests
  • 80.98% branch-aware coverage
  • Ruff formatting and linting
  • Strict mypy validation
  • Debian package and desktop-entry validation
  • Installed-package menu smoke test
  • Reproducible release assets, checksums, SBOM, and provenance

The framework remains passive by default. Active verification still requires an exact compatible
profile, a tested module, an isolated lab target, and explicit authorization.

Assets 9
Loading